2009/5/1 Michael DeHaan <[email protected]> > 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. > > IIRC cobbler check does already check Apache status, so > dnsmasq/BIND/dhcpd is fair game if management is enabled and > modules.conf points to those engines (patches accepted) -- though I > don't think that feature is really that important or worth > spending time on relative to other things already in Trac. (it's > technically correct, but I don't think it's really confused anyone > for more than a few seconds).
Sure! Trac is quite full of RFEs... Just an idea in the air :p > > --Michael > > > > > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler >
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
