Hi all,

I have a system set up to start certain netctl profiles on boot. In some cases, the system may boot before the network's DHCP server does, so that profile fails to start. I would like it if I could configure this netctl profile kind of like a systemd service with Restart=on-failure, so that after a little delay, it'll try to start again. Is there a way to do that?

Alternatively, might netctl hooks be a way to do this (I haven't read up on them yet)? Or will I have to do brute-force it and write a script that constantly checks if the profile is running and tries to start it if it isn't?

Thanks!

Wouldn't it be easier to start netctl only after the network is definitely online?
How are you starting it in the first place? Via systemd? That has options to start something after something.

I suppose it would, but how do I know if the network is definitely online before trying to bring up the interface with netctl? Also, if there is no DHCP server available, I still want the system to finish booting, and if the netctl profile times out, it never tries to start again. So, if the DHCP server eventually shows up, the profile wouldn't try to start up again.

systemd provides for all these scenarios & possibilities.
A good start: https://wiki.archlinux.org/index.php/Systemd

Yep, that's why I'm hoping netctl does as well, but as I mentioned in my post, I don't know how to do that, and it's not a function of systemd. As far as I am aware, the netctl profile does not allow you to set systemd-type options (like Restart and RestartSec). Is there a way to add a systemd-style unit file that configures how that profile should behave as a "service?"

How about ifplugd
https://wiki.archlinux.org/index.php/Netctl
https://jlk.fjfi.cvut.cz/arch/manpag...tctl.special.7
https://wiki.archlinux.org/index.php/Start/enable