Bug#433133: ASYNCMOUNTNFS=no

2007-07-19 Thread Steinar H. Gunderson
On Wed, Jul 18, 2007 at 05:28:42PM -0600, Bruce Sass wrote: This doesn't work for me, it kinda makes things worse because now the messages telling me that statd isn't running disappear off the screen before I can read them. OK, thanks. I can manually start rpc.statd, then mount the missing

Bug#433133: ASYNCMOUNTNFS=no

2007-07-19 Thread Bruce Sass
On Thu July 19 2007 03:01:30 am you wrote: I can manually start rpc.statd, then mount the missing nfs imports, but since /usr was missing during the boot there is bound to be stuff which didn't start properly. Is there a way to ensure everything is in order besides manually discovering

Bug#433133: ASYNCMOUNTNFS=no

2007-07-19 Thread Steinar H. Gunderson
On Thu, Jul 19, 2007 at 03:58:58AM -0600, Bruce Sass wrote: First thing I tried (with the -10 build, both by adding it to the options list in fstab and mount -o...), mount complained that nolocks was unsupported by(for?) nfs. Hm, that's interesting. I'll check it out at some point. I'll

Bug#433133: ASYNCMOUNTNFS=no

2007-07-18 Thread Bruce Sass
Try setting ASYNCMOUNTNFS=no in /etc/default/rcS. I'm currently talking to the initscripts maintainers to try to find a good solution; it seems like the fix in 1:1.1.0-10 introduced a race condition. This doesn't work for me, it kinda makes things worse because now the messages telling me