I wrote that init script for the debian packages. It predates the pid-file solution, and needs cleaning up. I'm on it.
Jesse Norell wrote: > On Fri, 2005-07-29 at 15:02 +1200, Simon wrote: > >>Hi There, >> >>Running on debian sarge. >> >>A month ago or so i updated from dbmail-mysql 2.0.4-0.20050211 to >>dbmail2-mysql 2.0.4-1.20050630. Since then we have had a few problems >>with dbmail IMAP and POP just stopping responding... On a restart this >>is the output: >> >># /etc/init.d/dbmail restart >>Stopping dbmail servers: start-stop-daemon: warning: failed to kill >>7396: No such process >>start-stop-daemon: warning: failed to kill 7030: No such process >>start-stop-daemon: warning: failed to kill 12179: No such process >>start-stop-daemon: warning: failed to kill 4780: No such process >>start-stop-daemon: warning: failed to kill 11477: No such process >>done. >> >>Where would i begin with this one? > > > Start with what OS/version and the contents of your /etc/init.d/dbmail > script. I'd guess start-stop-daemon is looking up pid numbers in > files (eg. from /var/run/ or somewhere) and trying to kill those, > but for whatever reason they're already dead. Another possibility is > it's using a "killall" which tries to signal every process of a given > name (eg. dbmail-pop3d), but once it kills the master (which itsself > kills it's children), some of the process id's have already exited > by the time start-stop-daemon gets to sending them a signal. > > You might also try "ps auxw|grep dbmail" prior to running your > init script, to see if those processes existed at the time (and what > they were) or not. > > > >>Regards >> >>Simon >>_______________________________________________ >>Dbmail mailing list >>[email protected] >>https://mailman.fastxs.nl/mailman/listinfo/dbmail -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
