You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current architecture seems for manager or global mode is when I pass any subsequent commands to daemon, they will be transferred to control process and my command will exits immediately without waiting for control process's response.
For example: dhcpcd --manager interface1 interface2
dhcpcd -4 -x interface1
It will exit after printing: sending commands to dhcpcd process
And control process will handle this command in background, I think it will be good if this command will wait for reply from control process and report success or failure depending on results.
Not sure if there is any existing option that I'm missing that could do this, will appreciate suggestions. I'm looking for a way to wait until control process has terminated dhcp4 from that interface.
Thanks for maintaining this cool project !!!
The text was updated successfully, but these errors were encountered:
Hi,
Current architecture seems for manager or global mode is when I pass any subsequent commands to daemon, they will be transferred to control process and my command will exits immediately without waiting for control process's response.
For example:
dhcpcd --manager interface1 interface2
dhcpcd -4 -x interface1
It will exit after printing:
sending commands to dhcpcd process
And control process will handle this command in background, I think it will be good if this command will wait for reply from control process and report success or failure depending on results.
Not sure if there is any existing option that I'm missing that could do this, will appreciate suggestions. I'm looking for a way to wait until control process has terminated dhcp4 from that interface.
Thanks for maintaining this cool project !!!
The text was updated successfully, but these errors were encountered: