Hi Steinar, 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.
But it's a bit of a chicken and egg situation. Mountnfs should wait till all interfaces that are configured to start automatically are up, or fstab needs options to specify the interface that the nfs shares will use (but that i feel is 'non standard'). 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. Cheers Phil Snowdon Senior Systems Engineer Actrix Networks On Thu, 2007-08-09 at 23:55 +0200, Steinar H. Gunderson wrote: > On Sat, Jul 28, 2007 at 12:32:28PM +0200, Steinar H. Gunderson wrote: > >> I have just returned from vacation and have quite a few things to catch > >> up with here. But I will take a look at it. I do hope that nothing else > >> breaks (dependencies) as I am running stable here. > > I can't guarantee that, sorry. There have been quite a lot of changes; I'd > > try to reproduce it on an unstable machine if I were you. > > Any progress on this? I'm starting to wonder if the best thing is just to > close it; there is no value in keeping a bug open if we do not really know if > it's fixed or not. > > /* Steinar */ > -- > Homepage: http://www.sesse.net/ > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
