FS#31958 - [systemd] unable to add service for eth1.

Attached to Project: Arch Linux
Opened by Caleb Cushing (xenoterracide) - Sunday, 14 October 2012, 20:56 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 14 October 2012, 21:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

~ # systemctl enable dhcpcd@eth1.service slave-iv
ln -s '/usr/lib/systemd/system/dhcpcd@.service' '/etc/systemd/system/multi-user.target.wants/dhcpcd@eth0.service'

from the looks of it it is creating the wrong service

following that this works

~ # systemctl disable dhcpcd@eth0.service slave-iv
rm '/etc/systemd/system/multi-user.target.wants/dhcpcd@eth0.service'

I'm guessing that simply making the link by hand will work
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 14 October 2012, 21:59 GMT
Reason for closing:  Upstream
Additional comments about closing:  https://bugs.freedesktop.org/show_bug.cg i?id=53954
Comment by Daniel Wallace (gtmanfred) - Sunday, 14 October 2012, 21:04 GMT
you should either make the link by hand or create a file in /etc/systemd/system that you can enable that has the [Install] section be how you want it, instead of enableing eth0
Comment by Daniel Wallace (gtmanfred) - Sunday, 14 October 2012, 21:11 GMT
when you enable services, it doesn't matter what you put after the @ for the instance, it will enable based on what is in the [Install] section of the service unit
Comment by Caleb Cushing (xenoterracide) - Sunday, 14 October 2012, 21:46 GMT
I'm just following the wiki. and noting that it's extra painful to get eth1 working given that the command doesn't work as expected. If the @ doesn't matter the wiki shouldn't document it as such.
Comment by Daniel Wallace (gtmanfred) - Sunday, 14 October 2012, 21:58 GMT
the @ does matter, but only when you are starting it, if you do systemctl start dhcpcd@eth1.service it will start eth1, but when you enable it, it will symlink to the instance that is defined in the service file

Loading...