Date: Fri, 31 Aug 2007 10:18:40 -0700 From: Sean Bruno <sbruno@miralink.com> To: freebsd-hackers@freebsd.org Subject: Re: rc functions don't allow processes to shutdown Message-ID: <46D84D70.50406@miralink.com> In-Reply-To: <alpine.BSF.0.999.0708311005210.72038@qbhto.arg> References: <46D84609.3080409@miralink.com> <alpine.BSF.0.999.0708311005210.72038@qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > 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. > Ah, as usual, I picked the wrong list. I'll take design issues there. > 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. > This may be symmetrical, but I question whether or not the 'correct' behavior is symmetrical. I don't see the benefit to the end user in this implementation, e.g. trying to disable a running service. If a new-ish admin edits the rc.conf prior to shutting down the service, there could be some consternation. However, my entire idea of how to shut down a process in FreeBSD may be flawed, and I may be the one who is in need of a 'design change'. :) Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46D84D70.50406>