Date: Fri, 31 Aug 2007 10:09:52 -0700 (PDT) From: Doug Barton <dougb@FreeBSD.org> To: Sean Bruno <sbruno@miralink.com> Cc: freebsd-hackers@freebsd.org Subject: Re: rc functions don't allow processes to shutdown Message-ID: <alpine.BSF.0.999.0708311005210.72038@qbhto.arg> In-Reply-To: <46D84609.3080409@miralink.com> References: <46D84609.3080409@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 31 Aug 2007, Sean Bruno wrote:
> I noticed that if rc.conf has ntpd_enable="NO", an invocation of
> /etc/rc.d/ntpd stop won't actually shut down ntpd. I checked a couple of
> other processes(like net-snmp) and noted the same behavior.
FYI, there is a list for discussing rc.d issues, freebsd-rc@. The current
behavior is by design, and I don't think that changing it is a good idea
this late in the game.
Assuming that lack of an affirmative _enable variable is a constant, the
only way that a service can be started is with either onestart or
forcestart. The symmetry here would be to stop it the same way.
> I would have expected that rc would be able to invoke the stop routines if a
> utility is disabled,
It can invoke them, in the same way that the start routines can be invoked
if a service is not enabled, by prepending one or force to stop.
Looking at this from the other direction, what would be the benefit to
having plain stop act in the absence of an _enable variable for that
service?
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.999.0708311005210.72038>