Right now it updates the 'settings' configuration file, as well as modules.conf on every client run.
>From what you're saying either of those files being changed would require a restart. However, looking in Git, neither of these files have been modified since February, so if I simply make Chef smart and only restart cobblerd when one of those file has *actually* changed, I should be in good shape. Thank you for your assistance! -Chris On Fri, Oct 24, 2014 at 6:17 PM, Alan Evangelista <[email protected] > wrote: > On 10/24/2014 06:27 PM, Chris Patti wrote: > >> I've been poring through the documentation and am trying to figure out >> under what conditions is a cobblerd restart actually required? >> > > Cobbler daemon loads collections and settings and initializes XML-RPC > server. > You should restart it when you update Cobbler collections/settings files > directly and when you update Cobbler code > > > We're currently restarting cobblerd with each and every chef client run, >> which means people aren't running chef very often, and I want to get all >> our machines into the standard every 1/2 hour chef run groove. >> > > I'm not familiar with Chef; what it does on each run? I need to know that > to be able to help you further. > > > Regards, > Alan Evangelista > > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler > -- Christopher Patti - Geek At Large | GTalk: [email protected] | AIM: chrisfeohpatti | P: (260) 54PATTI "Technology challenges art, art inspires technology." - John Lasseter, Pixar
_______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
