Here's a first cut that does (2) with a slight modification to mountnfs.
If DELAYNFS=yes is set in /etc/default/rcS then it will exit the script
unless all auto configured interfaces are up.
There may be a better way of figuring out which interfaces are set to
auto, but this ones works for al
Agree with Steinar. There are simple workrounds in most cases for Etch.
However the issues still need to be addressed in Lenny/Sid.
I can think of 2 solutions. One is to add an option to 'mount'.
similar in operation to _netdev, but with the ability to specify an
interface. Not too keen on
Yes. Just not quite as much as I would have liked.
Basically the issue seems to be resolved in Lenny. but the behavior is
slightly differnt to Etch.
Test setup here is machine with dual NICs. Debian Lenny installed and up
to date. DNS and NetApp NAS on 'backend' network (eth1). Primary
in
> 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 s
erfaces 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
5 matches
Mail list logo
