This failure to load with domain names in the config may have arisen with the network now set up by upstarts native /etc/init mechanism (instead of with symlinks in/ets/rc?.d) or been present all the time.
However, a proper fix should no be now to ship two firehol upstart definitions:
One /etc/init/firehol-first.conf (or -prenet, -init, -predns or -minimal?) definition that stats firehol (before any network/dns is up) with a corresponding /etc/firehol/firehol-first.conf .
And one /etc/init/firehol.conf definition that starts firehol (always after a network interface has come up) regulary.
This failure to load with domain names in the config may have arisen with the network now set up by upstarts native /etc/init mechanism (instead of with symlinks in/ets/rc?.d) or been present all the time.
However, a proper fix should no be now to ship two firehol upstart definitions:
One /etc/init/ firehol- first.conf (or -prenet, -init, -predns or -minimal?) definition that stats firehol (before any network/dns is up) with a corresponding /etc/firehol/ firehol- first.conf .
And one /etc/init/ firehol. conf definition that starts firehol (always after a network interface has come up) regulary.