Issue #5153 has been updated by R.I. Pienaar.
Nigel Kersten wrote: > > RI would you be ok with a method to signal the currently running daemon to > run, optionally providing it a splay, rather than invoking a whole new daemon? yes, I have 2 use cases now: * Run now * Run splayed I have another in mind: * Run with this tag, now or splayed. So I would have suggested the signal methed - I still think it would be a valuable feature in its own right - but I can see us needing more than what signals would allow. I think - untested - I can reasonably easily 'hack' around the problem by just telling it a different pid file - but the same lock file. This will give me the same capability as my request, but thats not nice. ---------------------------------------- Bug #5153: Ability to run --onetime in the background while a daemon is idle https://projects.puppetlabs.com/issues/5153 Author: R.I. Pienaar Status: Accepted Priority: High Assignee: Category: Target version: Affected Puppet version: 2.6.2 Keywords: Branch: When the puppetd daemon is running it has the pid file preventing other background daemons. When running --onetime --no-daemonize - a foreground run - this is fine, pid file doesnt prevent the --onetime run but if you wanted to do a backgrounded --onetime run the pid file will prevent that run from happening. We should arrange so that a backgrounded --onetime is allowed if the other daemon isnt actively also doing a run. Additionally if you do --onetime --splay 30 the new daemon should background and only bail out the run when it starts at the end of the splay period if the background daemon is then doing a run. The context of that from mcollective I'd like to schedule --onetime runs - with optional splay. In that case I start the puppetd in the background and report back if that was successful or not leaving the actual running up to the puppetd that will then have disowned itself from the mcollectived so it can run at its own schedule using splay or whatever is configured. This is possibly closely related to #3757 -- 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.
