I did find that the rc.local fix that was mentioned works, I didn't even
have to include the sleep command, just the mount -a -t nfs.
--
nfs shares not mounted at startup
https://bugs.launchpad.net/bugs/45842
You received this bug notification because you are a member of Ubuntu
Server Team, which
I confirm that this is still happening in karmic, I have the same issue,
and a lot of the fixes above either don't work, or the file that they
are changing doesn't exist to begin with. I'm running a fresh install
using kubuntu on an amd64 platform.
--
nfs shares not mounted at startup
https://bug
This appears not to be fixed in karmic. I have sysvinit-utils version
2.87dsf and my NSF mounts are not happening on reboot.
--
nfs shares not mounted at startup
https://bugs.launchpad.net/bugs/45842
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug
@Mateusz: your bug is different, as this precise one was fixed.
Yours looks a lot like bug 275451.
--
nfs shares not mounted at startup
https://bugs.launchpad.net/bugs/45842
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
--
Ubuntu-ser
Hello,
as you can guess I have the problem with mounting NFS at boot time.
My /etc/lsb-release is:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION="Ubuntu 9.04"
I've installed this system as VMware virtual machine (F4 during install
CD boot, etc.).
This bug is
I am running hardy-server x64 and this really sux.
Someone please explain why this is so:
sudo mount -a -t noproc,nfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs #
this does not work
sudo mount -a -t nfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,noproc #
This WORKS!!!
What kinda hacky thing is thi
Hi all!
I've just noticed that, if in the /etc/fstab file the server is inserted in the
form 'servername.local' (mDNS name), the NFS volume isn't mounted at boot time.
If, after the boot, I do "sudo mount -a" is ok: obviously the avahi-daemon is
not ready yet at boot time.
But the weird thing i
Hi-
I took a look at Bug #213444 and it does not appear to be related, in
my opinion.
Bug #45842 (this bug) was caused by a race condition, which
specifically only occured on boot.
The slowness of mount.nfs you speak of in Bug #213444 usually points
to an rpc/portmap or networking problem, in my
Is this bug possibly related to https://bugs.launchpad.net/ubuntu/+bug/213444";>Bug #213444,
recently reported in Hardy Heron, where auto mount now works, but where
the 'mount -a' command is extremely slow and issues unexpected messages?
--
nfs shares not mounted at startup
https://bugs.launchpad
sysvinit is a source package that contains, as well as sysvinit itself,
the sysv-rc script runner and initscripts that we still do use.
--
nfs shares not mounted at startup
https://bugs.launchpad.net/bugs/45842
You received this bug notification because you are a member of Ubuntu
Server Team, whi
I think upstart-compat-sysv provides the same sysv functionality is
sysvinit, which is why a bunch of stuff is going to be removed.
Perhaps a similar patch needs to be written for upstart?
--
nfs shares not mounted at startup
https://bugs.launchpad.net/bugs/45842
You received this bug notificati
I suprised that his fix only seems to affect "sysvinit" - I just ran
into this problem on Gutsy once again (very annoying) and noticed that
sysvinit is not installed on that box. This is an out-of-box 7.10
install with updates. "sysvinit" is in the list of packages that can be
installed, however, i
Just a question since I have never done any [start-script] patching
before: Should I run the command
patch -p0 < sysvinit_2.86.ds1-14.1ubuntu37.debdiff
(or -p or -p1?) in a root konsole, and all will be fixed?
This concerns Kubuntu 7.10 Gutsy laptops suffering from not having nfs
wlan-dis
13 matches
Mail list logo
