how to prevent "dhcpcd %iface%" from exiting if no IP received?

[perkelix]

Not a bug, as much as a question.

When launched via dhcpcd %iface%, the binary seemingly exits if no answer was received. Is there any command option that can be passed to make the binary fork to the background if the timeout has been reached and keep on waiting for a reply?

The --timeout option seems like it might do what we need, but the manual page's phrasing is ambiguous.

I'm asking because, if the binary exits, it makes ifup fail irreversibly. At that point, only a host to which the administrator has physical access can be logged onto to have a manual attempt at acquiring an IP, while remote hosts are essentially lost due to the binary exiting.

[rsmarples]

Is this a dupe of #413?

[perkelix]

No. The other one wants to wait for an error before exiting. This one wants to not exit and instead fork to the background to wait for an IP.