[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Policy Question: Startup Scripts and Config Files



On Tue, 17 Apr 2001, Marc Haber wrote:
> I have a package where the init script contains most of the package's
> functionality, and parses a free-format config file
> /etc/$PACKAGE.conf. That file is not a shell script and can't be
> directly sourced.
> 
> Can I keep that file as /etc/$PACKAGE, should I move it to
> /etc/default (probably not), or do I have to re-work that file as
> sourceable file that is then sourced by the init script?

I'm not sure. Since the initscript is most of your package, it makes some
sense not to dump its stuff in /etc/default.

> Do I need to keep the init script as a conffile even if there are "no
> admin serviceable parts inside"?

Most definately yes. You better have a damn very good reason (e.g: the world
will end in a flood of Microsoft-made bovine crap with a mint smell because
their marketing tried to use hordes of purple dinossaurs with shovels to
distribute it) to have a non-conffile anywhere in /etc.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Attachment: pgp1ZwvA9NIcv.pgp
Description: PGP signature


Reply to: