I solved the problem by adding a 'sleep 10' at the beginning of
mountnfs.sh. The root of the problem ought to be somewhere in
/etc/init.d/networking.
/Mattias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I have this problem too, on a recent (6/6/2006) install of etch.
The core problem is that the network is not available at the time mountnfs.sh
is run. The reason for this in turn is that the installer, not unreasonably,
configures the network as a hotpluggable device. The relevant stanza
of /et
Hi Steinar,
Am 2006-04-03 02:32:21, schrieb Steinar H. Gunderson:
> That sounds odd; could you try finding out what script it's depending on?
> Between 45 and 99 I can find mountnfs-bootclean (cleans /tmp),
> console-screen, alsa-utils, ntpdate, bootmisc (creates /var/run, saved dmesg,
> etc.), u
reassign 360123 initscripts
thanks
On Thu, Mar 30, 2006 at 06:03:40AM -0600, Robert Zeh wrote:
> It appears that nfsmount.sh runs to early in the boot process --- it always
> fails with a "no route to host" message.
>
> A ping added to nfsmount.sh is also unable to reach the NFS server.
That s
Package: nfs-common
Version: 1:1.0.6-3.1
Severity: important
It appears that nfsmount.sh runs to early in the boot process --- it always
fails with a "no route to host" message.
A ping added to nfsmount.sh is also unable to reach the NFS server.
I am able to mount the NFS file system when the
5 matches
Mail list logo
