FS#34956 - [dhcpcd] proposal: add dhcpcd-no-wait@.service

Attached to Project: Arch Linux
Opened by Marius (65kid) - Thursday, 25 April 2013, 18:30 GMT
Last edited by Anatol Pomozov (anatolik) - Thursday, 20 March 2014, 13:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

On my laptop, I want dhcpcd to watch both my wifi and ethernet interface. I can't use dhcpcd.service for this because it causes udev to fail to rename the network interfaces on bootup. I can't use dhcpcd@.service either because it is configured with the "-w" switch to wait for the interface to be up before the process forks. If, for example, there is no ethernet cable plugged in on bootup, the service will timeout and fail.

for this usecase I propose a dhcpcd-no-wait@.service which uses the "-b" switch instead of the "-w" switch. The process will then fork immediately and watch the interface.

I also noticed bug #33923 and thought of a way to fix this with the dhcpcd-no-wait@.service. I don't know if this would actually work and haven't tested it, but couldn't the arch iso just use a udev rule to start a dhcpcd-no-wait@.service on any renamed interface that comes up? Something like this:

SUBSYSTEM=="net", NAME!="", ENV{SYSTEMD_WANTS}="dhcpcd-no-wait@$name.service"

I bet there is a reason this doesn't work, but I thought I'd throw the idea out there.
   dhcpcd-no-wait@.service (0.3 KiB)
This task depends upon

Closed by  Anatol Pomozov (anatolik)
Thursday, 20 March 2014, 13:49 GMT
Reason for closing:  Won't fix
Additional comments about closing:  networkd makes this obsolete for me and there wasn't any response from the maintainers for almost a year anyway.
Comment by holos (holomorph) - Sunday, 17 November 2013, 19:32 GMT
Is there any reason the -w switch is used instead of -b? Seems pointless.
Comment by Kai Hendry (hendry) - Tuesday, 18 March 2014, 02:49 GMT
I'm confused to the extent of dhcpcd@.service functionality. Shouldn't wired interfaces be handled by systemd-networkd? http://dabase.com/blog/Good_riddance_netctl/
Comment by Marius (65kid) - Tuesday, 18 March 2014, 22:50 GMT
I opened this bug long before systemd-networkd was even in development stage. But yeah, I also use networkd now and don't care about this functionality anymore, and I guess the maintainers don't either, so I will close this.

Loading...