http://bugzilla.novell.com/show_bug.cgi?id=579944
http://bugzilla.novell.com/show_bug.cgi?id=579944#c8
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nfbrown@novell.com
Component|Bootloader |Installation
AssignedTo|nfbrown@novell.com |bnc-team-screening@forge.pr
| |ovo.novell.com
--- Comment #8 from Neil Brown 2010-02-25 20:00:23 UTC ---
I doubt this is related to rpc.idmapd.
Immediately after starting rpc.idmapd, /etc/init.d/nfs attempted to mount
any NFS filesystems required by /etc/fstab.
If, as you say, networking is not configured at this point, then this is going
to fail, and take quite a long time in failing. 3-4 minutes per mount point
does not seem at all unlikely.
Options:
- Add the 'bg' option to all the mounts. This will cause them to timeout
significantly more quickly, and continue retrying in the background.
- Don't use network manager, but rather use ifup to configure at boot time.
I appreciate that this might not be practical on a notebook.
- configure automounting to mount those 5 filesystems. That was the mount
wont even be attempted until you want to look a the content.
automounting is really the best option to use in conjunction with
network-manager.
Possibly the yast installer should not allow you to both choose network
manager and request nfs filesystems to be mounted at boot-time.
So I'm treating this as a configuration error, and reassigning to the
installer team so they can comment on whether or not it is possible to
make that error impossible with yast.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.