Issue #15911 has been updated by Robert Kennedy.
Whoops, I went on leave for an extended period and this totally fell through the cracks. As Calvin and Benjamin point out nodes with systemd 188+ won't have this problem. Fedora 18 ships with systemd 195. Ideally puppet could handle nodes of any vintage or detect the systemd version and act appropriately. Jeff rightly pointed out in the pull request that it may not be puppet's job to unify service naming. I agree with that in principle, especially for cross-provider and cross-platform handling. My only opposing thought is that this is internal to a single provider and the patch represents behavior that systemd itself eventually adopted. I have no firm opinion. Automatically appending .service would be nice to have and mirror what the newer systemctl does at the command line. The future probably holds a migration to socket and path activation for many services, so I've continued using a selector so it's abundantly clear if/when I disable foo.service and enable foo.socket. That's a personal choice though. I believe this only affects Fedora 15-17 users, since RHEL6 is still using upstart. I'm not sure about OpenSUSE. ---------------------------------------- Feature #15911: automatic .service suffix for the systemd provider to keep service names consistent https://projects.puppetlabs.com/issues/15911#change-96385 * Author: Robert Kennedy * Status: Code Insufficient * Priority: Normal * Assignee: * Category: service * Target version: * Affected Puppet version: * Keywords: systemd * Branch: https://github.com/puppetlabs/puppet/pull/1518 ---------------------------------------- I'd like to be able to be able to have a mix of systemd and redhat systems that run the same named services. Currently it seems I have to resort to <pre> $snmpservicename = $snmpserviceprovider ? { "systemd" => "snmpd.service", "redhat" => "snmpd", } service { "$snmpservicename": provider => "$snmpserviceprovider", etc. } </pre> I would much rather choose the provider for my system and be able to refer to the snmpd service with the same name across hosts with different providers if possible. I believe everything that puppet would want to handle as a Service would have a .service suffix. If you think it would cause too much confusion due to the assumption of service naming, I can continue to do what I'm doing. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
