Around 08:14pm on Sunday, June 20, 2010 (UK time), Karl-Olov Serrander scrawled:
I would guess that the network interface is not up yet.
https://bugzilla.redhat.com/show_bug.cgi?id=595386 might help.
Good call. Making the NETWORKWAIT=yes fix sugested there fixed it, and
is much better than
On Sat, 19 Jun 2010, Steve Searle wrote:
I have installed Fedora 13 on two machines now, and am getting the same
problem when mounting nfs shares at boot time on both machines. The
problem happens most of the time when I boot, but not always.
I have four nfs mounts and when the problem
I have installed Fedora 13 on two machines now, and am getting the same
problem when mounting nfs shares at boot time on both machines. The
problem happens most of the time when I boot, but not always.
I have four nfs mounts and when the problem occurs the following message
is displayed four
On Sat, 19 Jun 2010 16:03:44 +0100
Steve Searle wrote:
Does anyone have any ideas?
Does this machine also run bind as a local nameserver?
I found that the first lookups I do during boot always
fail. I assume because bind takes too long to get
started and prime the cache (or something :-).
I
On Sat, Jun 19, 2010 at 18:03, Steve Searle st...@stevesearle.com wrote:
I have installed Fedora 13 on two machines now, and am getting the same
problem when mounting nfs shares at boot time on both machines. The
problem happens most of the time when I boot, but not always.
I have four nfs
Steve Searle wrote:
I have installed Fedora 13 on two machines now, and am getting the same
problem when mounting nfs shares at boot time on both machines. The
problem happens most of the time when I boot, but not always.
I have four nfs mounts and when the problem occurs the following
Around 04:30pm on Saturday, June 19, 2010 (UK time), Tom Horsley scrawled:
On Sat, 19 Jun 2010 16:03:44 +0100
Steve Searle wrote:
Does anyone have any ideas?
Does this machine also run bind as a local nameserver?
I found that the first lookups I do during boot always
fail. I assume
Around 05:41pm on Saturday, June 19, 2010 (UK time), Bill Davidsen scrawled:
One possibility is that DHCP hasn't run yet, and albacore didn't map to
albacore.your.domain because /etc/resolv.conf didn't have the search path
set.
Try using the FQDN instead of just the node name and see if
