On Thu, 5 Sep 2002, eric pareja wrote:
> On Wed, Sep 04, 2002 at 08:35:28PM +1000, Rowel Atienza wrote:
> > cd /etc/rc5.d/
> > ./S13portmap stop
> > ./S14nfslock stop
> > mv S13portmap _S13portmap
> > mv S14nfslock _S14nfslock
>
> shouldn't those be renamed to K13portmap K14nfslock?
>
I used to do it that way (K13portmap K14nfslock) until I encounter
problems with solaris K scripts. The difference is when you prepend it
with K instead of _S, the shutdown or telinit command will try to find a
process to kill ( the K ) instead of simply ignoring it ( the _S ). If the
the K script is not written properly, it's either it will refuse to
proceed until it finds the right process pid to kill or it will generate
lots of garbage messsages.
I think it is a matter of choice. I choose renaming it with _S
instead of K because I want to avoid the extra overhead during shutdown or
telinit. The disadvantage is _S will not be probably recognized by daemon
monitoring/management tools like tksysv (which I dont use bec I believe
doing it by commandline is more sensible). Nonetheless, the _S way is
recommended by one of the Sun Blueprints on Security. For ease of
management between *nix platforms, I chose _S.
rowel
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
