unbound and (isc) dhcpd startup order

[Michael Gmelin]

On Tue, 16 Jun 2020 12:36:19 -0400
Ryan Steinmetz <zi at freebsd.org> wrote:

> On (06/16/20 08:14), Rodney W. Grimes wrote:
> >Ok, well, I just thought of one and not sure if it is an issue or
> >not, doesng unbound have the ability to specify interfaces?  If so
> >those may not exist until NETWORKING has run?
> >  
> 
> Unbound isn't really going to do anything useful without the network.
>  I don't think it is unreasonable that it should depend on NETWORKING.
> 
> I think we're in an edge case here and, perhaps, a better solution
> might be to have someone(tm) add in support in rc.conf to specify
> dependency overrides.
> 
> So, perhaps you could set:
> 
> dhcpd_after="unbound"
> 
> Which would factor into the rcorder processing and make sure that
> dhcpd starts after unbound.
> 
> This would allow people to fine-tune things when they run into cases 
> like this.

Exactly my thoughts for a while now. There are more examples like this
(e.g., you run a service and host the database in the same
jail/on the same machine, you want to have a dependency on the database
being up, etc.).

Never found the time to look into it though.

Cheers,
Michael


-- 
Michael Gmelin