Issue #18514 has been updated by Vincent Gallissot.
File vgallissot.systemd.puppet3.0.1.try.log added
Thanks for those fast answers !
Actually, I have 2 more comments to make :
1) I had to add the following in the top of my manifests to have 'systemd' as
the default provider for fedora > 15 :
`case $operatingsystem {
‘Fedora’: {
if $operatingsystemrelease > 15 {
Service{
provider => 'systemd'
}
}
}
}`
2) The systemd provider included in puppet 3.0.1 is not working for fedora <
18. Explanations :
It does for a start of service : `/bin/systemctl start autofs`
as in : "Error: Could not start Service[autofs]: Execution of '/bin/systemctl
start autofs' returned 1: "
It's not that way systemd works until Fedora 18 : On each service or target or
socket, you have to specify it after the ressource value.
For example if you want to start autofs :
`/bin/systemctl start autofs.service`
So, for all services, you have to specify '.service' after it, otherwise it'll
never work.
For the moment I kept the sysVinit retro-compatibility in Fedora 16. It's
working like that but it should be done the 'systemd' way.
For Fedora 18, systemd has be improved to be compatible with the way puppet
uses it. As in
http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html#idm37643664
:
`2.13.2. systemctl assumes it works with services
systemctl, the utility used to administer services and other systemd targets,
will now assume that it is working with a service. Administrators will no
longer have to append .service to the name of the daemon they are
administering. For example, systemctl restart dhcpd will now just work, but
previous releases required systemctl restart dhcpd.service.`
NB : systemd is the default on Fedora since Fedora 15. The Fedora dev team
asked developpers to make compatibility of their services for systemd since
that release.
I'll try systemd provider on Fedora 18 and I'll make you a feedback.
Thanks for your help,
Vincent Gallissot
----------------------------------------
Feature #18514: Auto using systemd commands on Fedora > 15
https://projects.puppetlabs.com/issues/18514#change-81211
Author: Vincent Gallissot
Status: Duplicate
Priority: Normal
Assignee:
Category: provider
Target version: 3.x
Affected Puppet version: 3.0.1
Keywords: provider initv systemd fedora
Branch:
I actually couldn't find how to make systemd the default provider on my agents.
I found that puppet will use systemd if we explicitly tell it to do so by
writing "provider => systemd,"
As 'chkconfig' and 'service' are not planned to work anymore on Fedora >= 18, I
don't really want to re-write all my modules to add a special case for fedora
and systemd.
I just want to know if it is hard coded that systemd will be the default
provider for Fedora >= 15 or have I to do it myself ?
In that case, what sould I modify ?
Thanks for your help
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" 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-bugs?hl=en.
