Issue #7273 has been updated by Noah Cantor.
Ben Hughes wrote: > This is because, I think (can confirm by running with debug), as it runs > invoke-rc.d puppet stop, and then would run invoke-rc.d puppet start... but > it can't, as you've killed puppet from within puppet. > > The way Nan suggests doing this is to make a cron job to start/restart puppet > if say a file is present. > > I am not 100% sure what would happen if you added "hasrestart => true" to it, > either. I imagine it would still fail. Would need to test it. Nan's solution sounds like a silly amount of overhead for a process which should just be able to reparse its config. Perhaps puppet should send itself a SIGHUP if the config file changes? After all, it runs in daemon mode all the time, anyway. ---------------------------------------- Bug #7273: Modifying puppet.conf causes 'reparsing config' and TERM signal results in shutdown of daemon https://projects.puppetlabs.com/issues/7273 Author: Randall Hansen Status: Investigating Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: ... waiting for details from Ryan Conway ... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
