help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Killed wrong proc!


From: Ted Zlatanov
Subject: Re: Killed wrong proc!
Date: 30 Sep 2004 14:41:19 -0400
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)

On Thu, 30 Sep 2004, architect@webalive.biz wrote:

On Thu, 29 Sep 2004, Ted Zlatanov wrote:

>> The reason why I only used "start" and "stop" in my example is
>> because those are the only standard options to /etc/init.d scripts
>> AFAIK.
>>
>> If I'm ignorant of any standards in this regard, I would appreciate
>> some pointers.  Unix startup/shutdown scripts seem to be stable
>> relative to a SysV hierarchy these days, with almost no pure
>> BSD-style startup/shutdowns, but I'm not aware of a standard.
> 
>       There is now:
> 
> http://refspecs.freestandards.org/LSB_2.0.0/LSB-Core/LSB-Core/iniscrptact.html
> 
>       It doesn't specify a lot.  On the other hand, if you want to know 
> what the generally accepted standards are, get a machine with as much 
> installed as possible, and do things like this:

> $ egrep -h '^[ A-Za-z]+\)' /etc/init.d/* | perl -ne 
> 'if(s/^\s*([A-Za-z]+)\).*/$1/){print}
>     106 stop
>     104 status
>     104 start

>       ...as we can see, status is as standard as start.  restart 
> (usually stop + start) and reload (usually something like
> killall -HUP) are also fairly popular.  After that, you get a variety of 
> exciting options, but unfortunately none of them are standard.

This, and the link you provided, are only valid for Linux,
unfortunately (I wish Solaris was a bit more modern in this regard,
but then again it has a lot of inertia).

Solaris:

cat /etc/init.d/* | grep stop | wc
     152     743    4278
cat /etc/init.d/* | grep start | wc
     212    1222    7444
cat /etc/init.d/* | grep status | wc
      16      89     573

I didn't refine the grep like you did, since obviously there's an
order of magnitude difference (most of the 'status' was from 3rd
party software, not Solaris stock startup scripts).  I would guess
other Unices are just as bad.

Anyhow, Mark, is there any chance that cfengine will support
startup/shutdown scripts as an option to processes: entries or are
we just running our mouths?  So far 3 people have expressed
interest in the feature.

Ted



reply via email to

[Prev in Thread] Current Thread [Next in Thread]