On Fri, May 1, 2009 at 10:22 PM, Michael DeHaan <[email protected]> wrote: > Fabien Dupont wrote: >> 2009/5/1 Jeff Schroeder <[email protected] >> <mailto:[email protected]>> >> >> On Fri, May 1, 2009 at 2:08 PM, Fabien Dupont <[email protected] >> <mailto:[email protected]>> wrote: >> > Hi. >> > >> > Another question today (I might be kind of brain heating today). >> > As far as I know, Cobbler generates config files and >> restart/reload the >> > services it manages (DHCP/DNS for instance) when syncing. >> > Why wouldn't it start them at boot time if they are managed ? Admins >> > would'nt have to mind about those services anymore, as cobbler >> would do it >> > for them. >> >> Is this too hard? :) >> >> >> Not that hard, but thank you for thinking of my (keyboard) health ;) >> I was just thinking of automating it as far as possible. >> The fact that cobbler manages those services could imply it manages >> also their start at boot. > > We're not going to reimplement chkconfig or start stopped services.
Couldn't you acheive the same thing by just running a 'cobbler sync' when the init script starts cobbler? Not saying you *should*, but it would be a minor tweak. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
