On 2012-07-30 12:01:08 +0200, Jonas Smedegaard wrote: > On 12-07-30 at 12:37pm, Andrei POPESCU wrote: > > 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: > policy.d. > > 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 > policyrcd-script-zg2.
There's a lack of documentation, with examples, e.g. on how to blacklist a daemon. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120730101609.gi6...@xvii.vinc17.org
