Issue #16125 has been updated by Daniel Pittman.
Josh Cooper wrote: > Puppet does not create a pidfile when running as a windows service. On Unix, > this happens in the `daemon.rb` code, but since we never daemonize on > Windows, this doesn't happen. Instead the daemon service wrapper needs to > create this so that mcollective can detect that the service is running and > signal it to run. So, it isn't clear to me why a pidfile is needed on Windows; shouldn't mcollective be able to stop, start, and restart the service using the standard Windows API for managing services? If it is required, what information should it contain? I guess the question is really, what sort of signal to run is supported on Windows? I assume something other than a POSIX signal... ---------------------------------------- Bug #16125: Puppet running as windows service does not create pidfile https://projects.puppetlabs.com/issues/16125#change-71222 Author: Josh Cooper Status: Accepted Priority: Normal Assignee: Category: Target version: 3.0.0 Affected Puppet version: Keywords: windows service pidfile Branch: Puppet does not create a pidfile when running as a windows service. On Unix, this happens in the `daemon.rb` code, but since we never daemonize on Windows, this doesn't happen. Instead the daemon service wrapper needs to create this so that mcollective can detect that the service is running and signal it to run. -- 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.
