In other words 128.93.24.32 doesnt seem to be running a lock daemon, or if
it is it wont talk to us
> this is the machine where the mail spool is stored.
> The problem disappears when i use the nolock option in mount.
It would "nolock" says don't do remote locking (thats equivalent to 2.0
behaviour)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/