Thanks for a quick response. I could use SC, but there are corner cases that require a lot of exec's and flow control, which looks quite ugly in Puppet. It would be nice if something like this was built in:
1. If service doesn't exist, create it (sc create) 2. Set recovery actions (sc failure) 3. Re-configure the service (sc config) to change command-line arguments 4. Disable recovery (sc failureflag) in case service crashes while stopping 5. Stop service (sc stop) 6. Wait for some timeout (since "sc stop" is async) 7. If the service is still up, kill the process (powershell stop-process) 8. Copy new files 9. Re-enable recovery (sc failureflag) 10. Start service (sc start) Regards, Igor. P.S. Yes, the version is 3.2.4. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
