Does your application startup script require NETWORKING?
Just a shot in the dark from a newbie.
-jgh
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_nfe0=UP
ifconfig_nfe1=UP
cloned_interfaces=lagg0
On Monday 27 July 2009 13:43:04 Peter Steele wrote:
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 an
entry in rc.conf defining
In the last episode (Jul 27), Peter Steele said:
We have an rc.conf file that looks something like this:
[...]
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
this could happen and are wondering how
the options in rc.conf are processed.
-Original Message-
From: Jason [mailto:jhelf...@e-e.com]
Sent: Monday, July 27, 2009 2:44 PM
To: Peter Steele
Cc: freebsd-questions@freebsd.org
Subject: Re: What order are options in rc.conf processed?
Does your
rc.conf is just a script that sets a bunch of environment variables for
the
/etc/rc.d/* scripts to use. The order the variables are set in that
file
does not matter. If you want your script to run after network
interfaces
are set up, you'll want to add a REQUIRE: NETWORKING line. See the
rc and
@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.
-jgh
On Mon, Jul 27, 2009 at 02:43:04PM -0700, Peter Steele thus spake:
We have an rc.conf file that looks something like
