Nerius Landys wrote:
> I am still bambuzzled by the network taking 30 seconds to come up.
One thing I've run into recently is an Ethernet switch that needs to
resolve spanning tree after a port reset. The physical link comes
back up quickly, but it seems to take about 30 seconds before the
swit
On Saturday 22 August 2009 21:11:01 Nerius Landys wrote:
> > I don't remember the original description, but any time I hear
> > about a 30 second "gap" during startup, I think of the well-known DNS
> > reverse look-up issue. Are you sure this is not the case here?
>
> Indeed, I have forgott
> I don't remember the original description, but any time I hear about
> a 30 second "gap" during startup, I think of the well-known DNS reverse
> look-up issue. Are you sure this is not the case here?
Indeed, I have forgotten to have the PTR record set up for my new IP address.
However t
Nerius Landys wrote:
I am still bambuzzled by the network taking 30 seconds to come up.
I don't remember the original description, but any time I hear about a
30 second "gap" during startup, I think of the well-known DNS reverse
look-up issue. Are you sure this is not the case here?
> calcru: runtime went backwards from 37332 usec to 16577
> usec for pid 47 (sh)...
Not to seem like I'm talking to myself, but I fixed this problem:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE-RUNTIME
(Turn off Intel® Enhanced SpeedStep.)
I am still bam
One last question. I'm getting interesting [kernel?] messages during
bootup. You know, the kind that are highlighted white in the console.
The relevant lines of rc.conf look like this right now:
defaultrouter="64.156.192.1"
hostname="daffy.nerius.com"
ifconfig_em0="inet 64.156.192.169 netmask
Thanks for the script. I found the underlying problem on my system.
My server is at a data center and I don't know what kind of equipment
the server is connected to. It appears that it takes 30 seconds for
the networking to start. I added this script as
/etc/rc.d/waitfornetwork, and enabled it i
On Fri, 21 Aug 2009 21:37:09 -0700
Nerius Landys wrote:
> Then why
> can't I do a lookup right after named starts?
Possibly it's a delay in bind being ready or maybe you don't have any
network access - the latter is common with ppp.
> By the way, the underlying issue that I'm trying to address
On Fri, Aug 21, 2009 at 09:37:09PM -0700, Nerius Landys wrote:
> I am trying to figure out why DNS lookups are not possible right after
> the "named" process has been launched (during bootup).
At start, named sends a couple of queries to e.g. root servers. All
this requires the network connection
