What order are options in rc.conf processed?

Peter Steele psteele at webmail.maxiscale.com
Mon Jul 27 22:05:48 UTC 2009

Well, if I understand what you mean, then yes, our app requires
networking. But it has two logic paths: If it sees the system has an IP
assigned it goes into one mode and if it does not have an IP assigned it
goes into another mode. In the case we've encountered the app takes the
"no IP assigned" path, even though we have an IP defined in rc.conf.
We're trying to understand how this could happen and are wondering how
the options in rc.conf are processed.

-----Original Message-----
From: Jason [mailto:jhelfman at e-e.com] 
Sent: Monday, July 27, 2009 2:44 PM
To: Peter Steele
Cc: freebsd-questions at freebsd.org
Subject: Re: What order are options in rc.conf processed?

Does your application startup script require NETWORKING?

Just a shot in the dark from a newbie.


On Mon, Jul 27, 2009 at 02:43:04PM -0700, Peter Steele thus spake:
>We have an rc.conf file that looks something like this:
>ifconfig_lagg0="laggproto failover laggport nfe0 laggport nfe1 <ip>
>netmask <mask>"
>In a recent reboot test, when "ourapp" started, it checked to see if an
>IP was assigned to the system and there was not, causing it to take an
>unexpected logic path. Our understanding though was that since we had
>entry in rc.conf defining the IP then our app should have started after
>that IP was assigned. Is this true or is there potentially a timing
>issue here?
>freebsd-questions at freebsd.org mailing list
>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"

More information about the freebsd-questions mailing list