On Dec 17, 5:18 pm, James Turnbull <[email protected]> wrote:
> An upstart provider for the service type should be fine. It should be
> relatively easy to develop. If you don't want to develop yourself can
> you please log a feature request and I'll knock something up.
>
> Cheers
>
> James
>
> --
> Author of:
> * Pulling Strings with Puppet
> (http://www.amazon.com/gp/product/1590599780/)
> * Pro Nagios 2.0
> (http://www.amazon.com/gp/product/1590596099/)
> * Hardening Linux
> (http://www.amazon.com/gp/product/1590594444/)
I'm not sure I'm up to developing this myself just yet as I'm very new
to puppet and haven't done any ruby thus far. I was about to create a
feature request, but then realized what you were saying about adding
upstart as a provider to the service type. I'm not sure that's
exactly what's needed. It's what I need, but perhaps would be wrong
for other uses of upstart. Upstart by design is event driven, so you
can have things like this:
# This task is run whenever the Control-Alt-Delete key combination is
# pressed. Usually used to shut down the machine.
start on control-alt-delete
exec /sbin/shutdown -r now "Control-Alt-Delete pressed"
Here's another example from Fedora 10 that shows even more diversity:
start on fedora.serial-console-available *
stop on runlevel [016]
instance
pre-start script
# script portion removed for brevity
end script
exec /sbin/agetty /dev/$1 $2 vt100-nav
post-stop script
# script portion removed for brevity
end script
I found the following page to be a quick, but informative read on some
of the capabilities: http://upstart.ubuntu.com/getting-started.html
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
