On Fri, Aug 19, 2005 at 02:36:53PM -0700, Joel Barker wrote: > You're right. Debian doesn't seem to provide any officially sanctioned way to > disable startup services (like Red Hat's chkconfig). This being so, disabling > services "by hand" should probably be considered "unsupported behavior": > people who do it (like me) must suffer the consequences. (It would be nice if > a future release of Debian supported this, thru a chkconfig-like program.)
Hmmm. Debian does actually provide one, it's called update-rc.d although you can shoot yourself in the foot if you don't use it properly. Most users will want something like sysvconfig, sysv-rc-conf or file-rc, they provide similar functionality to chkconfig. > For now, it would be better if cron could determine whether anacron is being > started in the current runlevel, instead of relying on roundabout solutions > like 'test -x /usr/sbin/anacron' or 'pidof anacron'. (It seems that trying to > let cron be ignorant of anacron won't work.) A possible solution would be > the following /etc/crontab (though I hate relying on an external script): I do dislike the need to rely on an external script (I actually wrote one recently for a similar purpose, see #307929) and I don't think cron should provide such a script even if it was needed for this. If a script was needed, it would be best if sys-rv would include it. Regards Javier
signature.asc
Description: Digital signature
