delayed network interfaces and ctdb service startup

[Steve French]

Ran into an issue with ctdb service startup failing (on RHEL) when
rebooting and there was a software update on the reboot (normally
works fine on reboot on next boot after software update (or before
software update etc.) but presumably network comes up late when
software update in progress).

Should ctdb service file be configured with something like

Restart=on-failure
RestartSec=60s

or Restart=on-abnormal ....

I noticed that ctdb was being started after networking, but presumably
that is not good enough to guarantee that socket is usable

[Unit]
Description=CTDB
After=network.target


-- 
Thanks,

Steve