On Mon, Nov 8, 2010 at 10:36 AM, John Poole <[email protected]> wrote:
> For kicks, I tried running the script now and was stopped because eth0 is > not starting (since I'm on wifi only at the moment). eth0 is a prerequisite > for mongodb. > > <snip> > The work-around for instances where one's service is dependent upon net returning true and you only have a wifi connection and eth0 is not connected is to modify the /etc/conf.d/rc file, such as I did: # RC_NET_STRICT_CHECKING allows some flexibility with the 'net' service. # The following values are allowed: # none - The 'net' service is always considered up. # no - This basically means that at least one net.* service besides net.lo # must be up. This can be used by notebook users that have a wifi and # a static nic, and only wants one up at any given time to have the # 'net' service seen as up. # lo - This is the same as the 'no' option, but net.lo is also counted. # This should be useful to people that do not care about any specific # interface being up at boot. # yes - For this ALL network interfaces MUST be up for the 'net' service to # be considered up. #RC_NET_STRICT_CHECKING="no" # # 11/8/2010 jlpoole below replaces above so mongodb starts on wifi # RC_NET_STRICT_CHECKING="none" -- John L. Poole P.O. Box 6566 Napa, CA 94581-6566 707-812-1323 [email protected] -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
