Re: PW#5-5: Standardized handling of /etc/init.d script options
On Thu, Jan 15, 1998 at 01:22:01AM +0500, Adam P. Harris wrote:
> "Christian" == Christian Schwarz <schwarz@monet.m.isar.de> writes:
> > On Wed, 14 Jan 1998, Steve Greenland wrote:
> >> On another note, what about things like cron, which don't *need*
> >> reload -- it tracks its conffiles, and reads them whenever they
> >> change. Should it just implement reload and force-reload as no-ops?
>
> > Yes, I think this would be best. (Some admins might not know this
> > and try to run /etc/init.d/cron reload, so it's best if it simply
> > does nothing.)
>
> Tut tut! What you really mean must be: does nothing but exits with a
> non-zero status. Or else we need to reword PW#5-5.
Is a non-zero status useful? After all, cron WILL reload
the configuration, even though that isn't caused by the script.
A reload will occur, which is success.
Hamish
--
Hamish Moffatt, hamish@debian.org, hamish@rising.com.au, hmoffatt@mail.com
Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5
CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
Reply to: