-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pidfile is the same when running with -T #396
Comments
That's an odd one. Running separate instances of dhcpcd works fine if it's not in test mode. I wonder what test mode does differently to end up with the same PID file. That's clearly a mistake. |
Why do you want to use test mode on many interfaces? Sounds like what you really want is the |
Also, I can't replicate this at all. When running in test mode a pidfile is never created by dhcpcd. |
Here is how to reproduce. Get a system with 2 network cards, echo them to the stdin of the script.
Output :
You see, they started to fight for the same pidfile. And its content is :
I need it to simply query DHCP server status on multiple interfaces without configuring them. Unfortunately So the solution would be to include interface name to the pidfile filename when running with -T. |
fixed on my side with |
--configure has all the information in the environment prefixed with _new. |
Pid file is the same regardless of interface name , when running with
-T
:/run/.pid
Therefore it is impossible to run multiple instances of
dhcpcd
on different interfaces in test mode.The bug doesn't exist in Ubuntu 22.04 ( dhcpcd 7.1.0) and appeared in Ubuntu 24.04 ( dhcpcd 10.0.6)
The text was updated successfully, but these errors were encountered: