Hi Kazutomo-san, On Mon, Nov 16, 2009 at 06:15:56PM +0900, NAKAHIRA Kazutomo wrote: > Hi Dejan, > [...] > >>QUIT signal for common linux process stop target process. > > > >From signal(7): > > > > SIGQUIT 3 Core Quit from keyboard > > > >i.e. there could be core dumps and I'm not sure if that's > >what you intend. > > > What I intend is that if syslog-ng process never stops > by the "kill -TERM", then trying core dump and stop process > by the "kill -QUIT". > [...] > I revised these parts and the syslog-ng RA's stop sequence is below. > > 1. Execute "kill -TERM" and wait KILL_TERM_TIMEOUT seconds > until syslog-ng porcess stopped. > 2. If sylog-ng process dose not stopped, then Execute > "kill -QUIT" to dump core and stop process.
I still don't understand why would you want a coredump of the syslog-ng process? Do you think that is really necessary? No other resource agent does that. Thanks, Dejan _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
