|
|||||||||||
|
Re: Waking up server during boot prevents NFS mounts after upgrade to etch
From: Bob Proulx <bob(at)proulx.com>
Date: Sun Jun 24 2007 - 23:48:21 EDT
This is probably related: http://lists.alioth.debian.org/pipermail/pkg-sysvinit-commits/2006-November/000923.html "It is useful to disable this on machines with the root file system in NFS until ifup from ifupdown work proberly in such setup." I did not research this problem to root cause but on the surface it appears that it is related to your issue. > The volumes get mounted eventually, but too late for a program that is Right. That is a bad side-effect. Instead the client should block and wait for the server. > With ASYNCMOUNTNFS=yes, the etch default, I get Glad to hear that the default is the one that works for you. > >Using sync versus async is completely different and unrelated. That I thought you were talking about the sync/async option. See this reference for more information. http://nfs.sourceforge.net/nfs-howto/ar01s05.html#sync_versus_async > I'm not quite sure whether to file a big report. In the end its my I think this would be covered by the 'initscripts' package. You may want to look to see if this is already reported in the BTS. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=initscripts;dist=unstable Bob -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Sun Jun 24 23:48:36 2007 This archive was generated by hypermail 2.1.8 : Sun Jun 24 2007 - 23:50:02 EDT |
||||||||||
|
|||||||||||