> The other options I can see are fiddling the timeouts in the mount
> options, or using fuser to kill things off before umount. As I said
> earlier, the mount options hard/soft/intr are useless in this case
> (no way to pass any signal to the blocking process).
RTFM,
man nfs
soft If an NFS file operation has a major timeout
then report an I/O error to the
calling program. The default is to continue
retrying NFS file operations
indefinitely.
timeo=n The value in tenths of a second before sending the
first retransmission after
an RPC timeout. The default value is 7 tenths of
a second. After the first
timeout, the timeout is doubled after each
successive timeout until a maximum
timeout of 60 seconds is reached or the enough
retransmissions have occured
to cause a major timeout. Then, if the filesystem
is hard mounted, each new
timeout cascade restarts at twice the initial
value of the previous cascade,
again doubling at each retransmission. The
maximum timeout is always 60 seconds. Better
overall performance may be achieved by increasing
the timeout
when mounting on a busy network, to a slow server,
or through several routers
or gateways.
retrans=n The number of minor timeouts and
retransmissions that must occur before a
major timeout occurs. The default is 3
timeouts. When a major timeout
occurs, the file operation is either aborted
or a "server not responding"
message is printed on the console.
Rex
