On Sun, Jan 23, 2005 at 10:53:48AM -0600, Steve Greenland wrote: > On 20-Jan-05, 22:09 (CST), Dan Jacobson <[EMAIL PROTECTED]> wrote: > > Sure, one can go behind the backs of maintainers with > > > http://www.debian.org/doc/manuals/securing-debian-howto/ch3.en.html#s3.6 > > > ("Disabling daemon services") > > and hope you remember what you did. But it's not as friendly as > > the approaches more and more packages are taking, as seen in my > > /var/log/boot: > > There is nothing more unfriendly than having > > '/etc/init.d/foo start' > > fail because because of some non-standard bit of crap in > /etc/default/foo. I could tolerate it if packaged defaulted *on*, but it > seems the habit is to default off. And more importangly, as others have > said (every single time this comes up), there is an *existing* mechanism > to accomplish this that doesn't require modifying every daemon package: > invoke-rc.d and policy-rc.d. >
Amen. I found this with distcc the other day. I had to dpkg-reconfigure it and answer yes to starting it on boot to be able to start it manually via /etc/init.d It almost needs to be a question as to whether you want the start link in /etc/rc?.d/ regards Andrew -- linux.conf.au 2005 - http://linux.conf.au/ - Birthplace of Tux April 18th to 23rd - http://linux.conf.au/ - LINUX Canberra, Australia - http://linux.conf.au/ - Get bitten! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
