On Fri, Aug 10, 2007 at 03:16:28PM +1200, Phil Snowdon wrote: > I wouldn't like to see this bug dropped as we still have issues with it. > My understanding is that mountnfs tries to mount the NFS shares as soon > as the first interface is available. We worked round this by changing > the order that the interfaces are brought up. from 'auto eth0 eth1' to > 'auto eth1 eth0'. However this has the side effect that the mount still > failed as the DNS server was off eth0. Final workround was to have a > seconday DNS server available off eth1.
Mm, that's interesting. However, in the present case, the mounts should really be backgrounded, and then come up as soon as the network is properly available. I won't guarantee that this can deal with not having a DNS server, but correct backgrounding behavior should make your original scenario "just work". If it doesn't, we'll need to figure out what goes wrong. > If you need me to do some testing with an 'unstable' system then I will. > But I don't want to repeat work that someone else is already doing. I'm pretty sure nobody else is testing this (it's not a very common setup), so please do test it. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
