Re: autofs - blocking system
H. Peter Anvin (hpa@transmeta.com)
30 Jun 1998 19:27:27 GMT
Followup to: <199806301745.TAA01541@gibbs.physik.uni-konstanz.de>
By author: Bernd Rinn <bernd@gibbs.physik.uni-konstanz.de>
In newsgroup: linux.dev.kernel
>
> while using autofs with the 2.0.34-Kernel we experience lock-ups of
> shells, when the shell tries to execute programs, that are available
> over NFS/autofs-directories from NFS-servers currently unavailable. We
> use non-blocking-operation for NFS-mounts (parameter 'intr' in each
> auto-map) and indeed you can break a 'ls <dir>', where <dir> is a
> autofs'd directory on an NFS-server, that is currently
> unavailable. But if you try to start a program (especially if you have
> such a directory in your path), the shell locks, no way to escape
> (only when the NFS-server gets available again). Is it possible to
> avoid this nasty behaviour under 2.0.34? (If not, does anyone know, whether
> it occurs under 2.1.xxx, too?). Thank you for your help.
>
It *should* be interruptible, but I no longer maintain the 2.0.x
branch of the code, so if it's broken, it will stay that way.
-hpa
--
PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See http://www.zytor.com/~hpa/ for web page and full PGP public key
I am Bahá'í -- ask me about it or see http://www.bahai.org/
"To love another person is to see the face of God." -- Les Misérables
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu