Skaag Argonius wrote:
So what does your final 'run' file look like for the 'log' process?Skaag
Any problem in multilog !processor and then qpsmtpd is blocked. The symptoms were a zero length "current" file, possibly a @*.u and "previous" file, and qpsmtpd would act as if not on the port at all. I think that means it really is as simple as "man multilog" says, using a qpsmtpd/log/processor script like this #!/bin/sh cat # perl_script sleeps 5 seconds, then processes the # most recent @*.s file-- ./perl_script & Then we would see no @*.u files or "previous" file except possibly after a shutdown. And the processor script may not have to know how to deal with @*.u or "previous" file because multilog will simply cat those together with "current" after startup, and then !processor be called, and work on the last @*.s file as usual. The qpsmtpd/log/run would be #!/bin/sh export LOGDIR=./main [ -d $LOGDIR ] || mkdir -p $LOGDIR exec setuidgid qmaill multilog t s1000000 n200 \ !./qp_log_s $LOGDIR -Bob
