> To reproduce the problem:
> - - mount some nfs from a server in your lan.
> - - Open an app, that uses the mounted fs. I've simply opened a
> konqueror-window for the directory where the nfs is mounted.
> - - shut down or crash the server or just pull the network-cable.
> - - Now the konqueror-process is nonkillable in D state. There's no
> chance to kill it.
does the problem persist after you reconnect the network cable?
what happens when the server becomes available again?
are you mounting with UDP or TCP?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 06 May 2003 17:47, Lever, Charles wrote:
> does the problem persist after you reconnect the network cable?
> what happens when the server becomes available again?
no. If server is available again, the process wakes up from D.
But like man mount says:
[snip] The process cannot be interrupted or killed unless you also specify intr. [/snip]
The process should be killable while the cable is pulled.
But that's not the case, although intr is in fstab.
> are you mounting with UDP or TCP?
uh. How to find it out? :)
- --
Regards Michael B?sch
http://www.8ung.at/tuxsoft
17:53:19 up 1:44, 5 users, load average: 1.04, 1.05, 1.06
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+t9s0oxoigfggmSgRAkDPAKCFMeEGvS3KUhwn0bNQngKRK6h2fwCdEcv/
U2ttfZ6Mm8Sazuksfn4UUrY=
=M5Kh
-----END PGP SIGNATURE-----