On 12-07-30 at 12:37pm, Andrei POPESCU wrote:
> On Lu, 30 iul 12, 11:12:43, Vincent Lefevre wrote:
> > On 2012-07-29 21:43:57 +0200, Wouter Verhelst wrote:
> > > An ENABLE switch does more than just disabling the run-at-boot
> > > state of an initscript. While I can buy the argument that some
> > > packages should not start *at boot* by default,
> > The problem is not just at boot, but also when pacakges are
> > installed (first install or upgrade).
> > > I do believe that whenever an initscript is called with the
> > > argument "start", it should bloody well start, and not exit after
> > > doing nothing because I haven't edited some scarcely related file
> > > somewhere.
> > As long as scripts are allowed to execute init scripts directly with
> > "start" or "restart" (see rsync postinst script, for instance), this
> > must not be the case. Otherwise there would be no means to disable a
> > daemon (uninstalling the package would not be a satisfactory
> > solution because the client may still be useful, such as with
> > rsync).
> I'd say there is a need for:
> 1. a system-wide setting to start daemons or not on boot/upgrades/etc.
> 2. a blacklist - daemons listed here should not start no matter what
> 3. a whitelist - daemons listed here should start no matter what
> This should satisfy all camps
That should be simple to setup, as the infrastructure exist already:
What I do locally to suppress starting daemons inside chroots is use
policyrcd-script-zg2 and then add a [custom script]. That script should
be easily changed/extended e.g. using "run-parts --list", and either
published at our wiki or released in a package conflicting with
[custom script]: http://source.jones.dk/?p=sbin.git;a=blob;f=policy-rc.d
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private