On Mon, August 25, 2008 20:03, Adam Jacob wrote:
>
> On Mon, Aug 25, 2008 at 1:17 AM, Brice Figureau
> <[EMAIL PROTECTED]> wrote:
>> Yes, that was also my plan, but I only had a daemontools environment
>> when I started, so that was the low hanging fruit.
>>
>> What would be the best way to detect runit and/or daemontools?
>
> My guess would be the presence of 'sv' indicates runit, and 'svc'
> indicates daemontools.
That makes sense. But the more I think about autodetection, I don't think
it will be possible.
To get daemontools/runit running in your service you need the following:
service {
"myservice":
provider => "daemontools"...
}
otherwise it will default to initscripts (or whatever is the default on
your platform). I can use a "defaultfor" but it seems to depends on facts,
so if you don't have a fact to say you are running runit in place of the
initscripts, then game over.
I fail to see (but maybe someone will have a good idea) how I can change
on the fly the provider.
> Let me know if you would like a runit host to test this on - I would
> be happy to provide you access to an EC2 node.
Thanks for the offer, but that won't be necessary, I'll setup a virtual
machine on one of my servers.
--
Brice Figureau
Days of Wonder
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
