Stephen Bosch <[EMAIL PROTECTED]> wrote:
>> my /var/log/maillog fills up with stuff like this:
>>
>> Jun 12 14:09:12 hotcube qmail: 992376552.411296 end msg 1005715
>> Jun 12 14:09:12 hotcube qmail: 992376552.507199 new msg 1005716
>> Jun 12 14:09:12 hotcube qmail: 992376552.507323 info msg 1005716: bytes
>> 266 from <[EMAIL PROTECTED]> qp 27390 uid 502
>> Jun 12 14:09:12 hotcube qmail: 992376552.573170 end msg 1005716
>> Jun 12 14:09:12 hotcube qmail: 992376552.660653 new msg 1005715
>> Jun 12 14:09:12 hotcube qmail: 992376552.660776 info msg 1005715: bytes
>> 266 from <[EMAIL PROTECTED]> qp 27403 uid 502
>> Jun 12 14:09:12 hotcube qmail: 992376552.732709 end msg 1005715
>>
>> and so on, and so on, and so on. It goes back months like this (I would
>> never have noticed it had it not been for some other issues I was
>> working on). Is this normal? My other qmail installations don't do that.
It's normal for qmail-send to log its actions. It's not normal to see
messages "end" without a delivery being logged, or for no "status:"
messages to be logged. It's not normal to have a qmail-send/log
service when you're logging via splogger/syslog.
>> [root@hotcube qmail]# /etc/rc.d/init.d/qmail stat
>> qmail-send: up (pid 27564)
>> qmail-smtpd: up (pid 27566)
>> qmail-send/log: unable to open supervise/ok: file does not exist
>> qmail-smtpd/log: unable to open supervise/ok: file does not exist
That means supervise isn't running for the log services.
>> Okay. So I checked for sticky bits on the appropriate directories:
>>
>> [root@hotcube supervise]# ls -ld /var/qmail/supervise/*
>> 927870 drwxr-xr-t 4 root qmail 1024 Sep 1 2000
>> /var/qmail/supervise/qmail-send/
>> 712830 drwxr-xr-t 4 root qmail 1024 Dec 18 10:27
>> /var/qmail/supervise/qmail-smtpd/
Were they set when the services were started?
>> qmail-smtpd/log:
>> 733311 -rwxr-xr-x 1 root qmail 94 Sep 1 2000 run*
No "supervise" directory... Further evidence that supervise isn't
running.
-Dave
