[Bug 551544] Re: puppet in lucid does not support upstart status

2010-03-31 Thread Nigel Kersten
I'll try and find the bug in a second, but apparently the lack of any
return codes from /etc/init.d/foo status when a service has been
upstarted is a bug.

Ultimately I feel puppet needs an initctl based service provider.

-- 
puppet in lucid does not support upstart status 
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 551544] Re: puppet in lucid does not support upstart status

2010-03-31 Thread Nigel Kersten
To clarify, assuming the status situation with upstarted init.d scripts
is resolved, I don't see any major reason why the existing provider
wouldn't continue to at least function well enough for users?

The update-rc situation isn't ideal, which is why I suggested an initctl
based provider, which really should be trivial to write given it already
supports start, stop, status and list.

I don't see Puppet upstream integrating such a provider into the 0.25.x
series as the commit rules are now for no new functionality to go into
minor updates in a release series, but if someone puts it together soon,
it can definitely make it into 'rowlf', the next major version.

-- 
puppet in lucid does not support upstart status 
https://bugs.launchpad.net/bugs/551544
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs