Re: Killed wrong proc!

[Chip Seraphine]

Because the restart command will not run unless I send either a TERM or a 
KILL, according to the reference.  'tis a hackaround.  I could have it set a 
class and then let shellcommands execute the restart, but that is even 
kludgier.

It would be nice if we could say signal=dorestart or something like that to 
clue cfengine that we want to execute the restart line without sending a 
signal.  (Or just allow signal 0 along with TERM and KILL, perhaps.)

Given that I have to send a signal, the reason for saying "restart" instead of 
"start" is that some Linux init scripts (esp with RedHat and SuSE) sometimes 
clean up pidfiles and such, IIRC.  Doing a restart instead of a start makes 
you less likely to run into ugliness.  The postfix script is not one of 
these, but it can't hurt.

On Wednesday 22 September 2004 09:15, Ted Zlatanov wrote:
> On Tue, 21 Sep 2004, chip@trdlnk.com wrote:
> 
> > In cfengine 2.1.10 on Solaris 2., this processes block:
> >             "postfix"
> >                     signal=TERM
> >                     restart "/etc/init.d/postfix restart"
> 
> Out of curiosity, doesn't the /etc/init.d/postfix script do the TERM
> signal for you?  I know it's not what you're asking, but I'm trying to
> figure out why you're going around the normal mechanism for restarting
> Postfix.
> 
> Ted
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine
> 

-- 

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com