[EMAIL PROTECTED] wrote: >Still having the service lock problem -- thanks Dave, I've followed >your suggestions here: > >>The general approach to fixing this problem is: >> >> 1) Stop all qmail-related processes including svscan, supervises, >> anything running as a "qmail" user, qmail-send, multilogs, >> etc. *Everything*. > >ps -a shows no qmail related services running prior to sending the >start command. If I let the error loop in one term window I see >svscan and TWO service entries (with one or both <defunct> >depending on how quickly I run ps). I looked for clues as to the >origin of the two instances, but couldn't find anything obvious. You mean "supervise"? You should see four: one each for qmail-send, qmail-smtpd, and two for "log"--the logs associated with them. >> 2) Double check directory names/owners/groups/modes and the >> contents of "run" scripts against LWQ. Check for extraneous >>ampersands (&) at the ends of lines. > >I have probably messed this up from standard... I recursively set >ownership of /var/qmail/supervise and its subdirectories to >qmaill.nofiles. The directories I opened up to 777. I reran the chmod >commands in LWQ on the run files in those directories setting >them to 755. I have no idea whether these changes would make >my problem worse, but the results have not changed... Post the output of the following: ls -lR /var/qmail/supervise cat /var/qmail/supervise/*/run cat /var/qmail/supervise/*/log/run -Dave
