2009/5/1 Jeff Schroeder <[email protected]> > On Fri, May 1, 2009 at 2:08 PM, Fabien Dupont <[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. chkconfig --add named > chkconfig --add dhcpd > chkconfig --add cobblerd > > Actually it does make sense for cobblerd to complain if it is set to > manage a service that isn't up. However that service should be > restarted the next time you "cobbler sync". > > -- > Jeff Schroeder > > Don't drink and derive, alcohol and analysis don't mix. > http://www.digitalprognosis.com > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
