Thanks, Christopher, for the feedback. This is indeed a linux system. For some reason the pid file is getting the pid of the child process. I'm generating the pid file with the command:
/sbin/pidof -s /usr/bin/slony1-cluster1 This doesn't seem to specifically get the pid of the parent process though. -----Original Message----- From: Christopher Browne [mailto:[email protected]] Sent: Tuesday, September 29, 2009 3:23 PM To: Michael Holt Cc: [email protected] Subject: Re: [Slony1-general] Slony init.d script help I presume this is on Linux? Linux reports each thread as a separate entry in the process table, which is why you'd see more processes than you have slons. Notice that 16149 is a child of 13894, which is quite consistent with this. The PID file gets generated by the main thread, and so killing that should also kill off any child threads. You might want to check the contents of the PID file to verify that. -- (reverse (concatenate 'string "ofni.sailifa.ac" "@" "enworbbc")) Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three" _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
