On Sun, Aug 24, 2008 at 11:41 AM, Brice Figureau <[EMAIL PROTECTED]> wrote: > > > This path adds a service provider to manage daemontools[1] > services directly from puppet. > > The daemons directories should be placed in /var/lib/service > (overridable with the service path parameter). > When the service is enabled, the daemon directory is symlinked > into the service directory which defaults to /service > (or /etc/service on debian). The daemon is then started by svscan. > Services are disabled by removing this symlink. > Start and stop are almost directly mapped to enable/disable. > This provider supports restart and status directly > > Comments are welcome.
As a big user of runit (a daemontools descendant) I'm glad to see a native provider for this. One of the things that might be great would be to add the capability to auto-detect whether you are using daemontools or runit, as the basics of the providers are identical, but with different command-line tools (svc for daemontools, sv for runit). Think you could add some auto-detection in there, so that runit/daemontools just happens based on which tool you are using? Also, if you've never heard of runit, imagine a maintained version of daemontools, with some smart additional functionality (such as service start post verifiction, a much improved multilog, and more) Adam -- HJK Solutions - We Launch Startups - http://www.hjksolutions.com Adam Jacob, Senior Partner T: (206) 508-4759 E: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
