Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names

[Dominic Cleal (JIRA)]

Title: Message Title

Dominic Cleal commented on an issue   Re: [meta] please stop arbitrarily changing systemd service unit names Sorry for re-opening this, but one issue with the symlink appears to be that systemctl enable throws an error when trying to enable it at boot. For example: [root@foreman-f19 ~]# rpm -q puppet puppet-3.4.2-1.fc19.noarch [root@foreman-f19 ~]# systemctl status puppet.service puppetagent.service puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; disabled) Active: inactive (dead) puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; disabled) Active: inactive (dead) [root@foreman-f19 ~]# systemctl enable puppetagent.service Failed to issue method call: No such file or directory [root@foreman-f19 ~]# systemctl enable puppet.service ln -s '/usr/lib/systemd/system/puppet.service' '/etc/systemd/system/multi-user.target.wants/puppet.service' systemctl start/stop appear to work normally though. Just trying to figure out at the moment how to support this and the package in Fedora itself, which doesn't have this change yet. Add Comment   Puppet / PUP-1200 [meta] please stop arbitrarily changing systemd service unit names In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.