Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 06 Jul 2000 23:50:43 -0700
From:      Doug Barton <DougB@gorean.org>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        Thomas Gellekum <tg@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: src/etc rc.shutdown
Message-ID:  <39657DC3.7D96BEC4@gorean.org>
References:  <200007070044.RAA03203@netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote:
> 
> Robert Watson wrote:
> >
> > So, generally, my observation for rc.d scripts was that previously, they
> > never even looked at the arguments, so running (whatever) stop will
> > actually run additional copies of the service on shutdown, if
> > /usr/local/etc/rc.d is not updated.  Is this correct?
> 
> I have previously implemented /etc/shutdown.d and /usr/local/etc/shutdown.d
> to avoid the confusion about what happens when /etc/rc.shutdown
> calls "/usr/local/etc/rc.d/apache.sh stop" and the old apache.sh doesn't
> check $1 and starts up instead.

	Personally I'm a little disappointed that this didn't get more discussion,
say on -arch. I think that changing the existing interface is a POLA
violation. I would support making a shutdown directory, or potentially even
making rc.shutdown more useful so that it calls the scripts for those apps
that need them specifically would be better solutions. 

Doug


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39657DC3.7D96BEC4>