1) Qmail, the Mail Transport Agent, failed to even start up. Haven't
finished tracking down the error messages associated with that one yet.
2) While I was investigating Qmail, I noticed the following error
messages in syslog:
Aug 18 17:01:53 phoenix ftpd[317]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:53 phoenix ftpd[147]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:54 phoenix ftpd[317]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:54 phoenix ftpd[147]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:55 phoenix ftpd[317]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:55 phoenix ftpd[147]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:56 phoenix ftpd[317]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:56 phoenix ftpd[147]: sleeping: flock of pid file failed: Invalid argument
Aug 18 17:01:57 phoenix ftpd[317]: sleeping: flock of pid file failed: Invalid argument
Switched back to 2.0.30 and everything was back to normal. Qmail came
right up and no ftpd error messages...
I build 2.0.31-pre7 by running make xconfig and then loading the
config from the 2.0.30 build and then saving it and building the 2.0.31-pre7
so I don't think I changed anything from one build to the next. Mandatory
locking IS enabled in both builds. Something broken in flock would account
for the Qmail failure, but I still need to confirm that from the error logs.
Regards,
Mike
-- Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com (The Mad Wizard) | (770) 925-8248 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!