Re: not starting daemons at boot: ln -s disabled
On Sat, Aug 06, 2005 at 12:15:29PM -0500, John Hasler wrote: Dan Jacobson writes: But the downsize is later, unless one keeps records, one isn't quite sure of just what tampering one has done in /etc/rc?.d/ Sysvconfig keeps records. Sweet. Now I get a Red Hat-like service command as well. Nice. regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: not starting daemons at boot: ln -s disabled
Dan Jacobson wrote: One way of having some daemons not start at boot (e.g., if we only use our printer once a year) is to remove certain /etc/rc?.d/ links. Hmmm, does init respect policy-rc.d? If so, it'd be fairly easy to do it that way... How many rc.d managers are in Debian anyway? policy-rc.d update-rc.d (this is the only one installed on my system) sysvconfig Any others? This seems excessive! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: not starting daemons at boot: ln -s disabled
Joe Smith writes: policy-rc.d update-rc.d (this is the only one installed on my system) sysvconfig Any others? This seems excessive! Update-rc.d and sysvconfig do not do the same thing. Read the man pages. And policy-rc.d is not an rc.d manager. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: not starting daemons at boot: ln -s disabled
Dan Jacobson wrote: One way of having some daemons not start at boot (e.g., if we only use our printer once a year) is to remove certain /etc/rc?.d/ links. Hmmm, does init respect policy-rc.d? If so, it'd be fairly easy to do it that way... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: not starting daemons at boot: ln -s disabled
On 05-Aug-05, 16:22 (CDT), Dan Jacobson [EMAIL PROTECTED] wrote: One way of having some daemons not start at boot (e.g., if we only use our printer once a year) is to remove certain /etc/rc?.d/ links. But the downsize is later, unless one keeps records, one isn't quite sure of just what tampering one has done in /etc/rc?.d/ mv S20foo s20foo Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: not starting daemons at boot: ln -s disabled
Dan Jacobson writes: But the downsize is later, unless one keeps records, one isn't quite sure of just what tampering one has done in /etc/rc?.d/ Sysvconfig keeps records. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
not starting daemons at boot: ln -s disabled
One way of having some daemons not start at boot (e.g., if we only use our printer once a year) is to remove certain /etc/rc?.d/ links. But the downsize is later, unless one keeps records, one isn't quite sure of just what tampering one has done in /etc/rc?.d/ So in /etc/default/* we can set NO_START_AT_BOOT=1 etc., at least we can see and comment what we did. However there still is a way to know what we tampered with in /etc/rc?.d/: instead of telling the user to just remove some links, have them instead ln -s to /dev/null or better: /etc/init.d/disabled perhaps, an empty file mode 555. And those link manager programs could do the same. So then one could see clearly that S20cwdaemon - ../init.d/disabled etc. Or use DISABLED for extra clarity. Not as efficient as removing the link, but at least one can see what one did later. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
