-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Friday 2007-04-20 at 10:27 -0700, Randall R Schulz wrote:
> > My guess is that the nfs session refuses to umount because there is a
> > user process (the one doing the halt) running from there. Or the halt
> > process is a child of kdesu that is running as user, or something of
> > the sort.
>
> Almost certainly this is the correct explanation.
>
>
> > > I experienced such behaviour with all OpenSuse 10.x versions, on
> > > different machines, both i386 and x86_64 platforms.
> >
> > You could open a bugzilla... I don't know if this is expected
> > behaviour, or if some option in the nfs mount can help.
>
> I wouldn't do that. It's not a bug that umount fails if there are files
> open on the file system in question (including current working
> directories).
You are right, I was too fast; but there is one exception: when halting.
I don't remember the exact sequence, but first process are politely
killed, after some seconds the remaining are then forcibly killed, then
filesystems are umounted. As there are no longer processes running, except
init and maybe something else, there can not be anything opened that
disallow umount. The exception might be the "/" mount, which is flushed
instead, I think. I would have to read it up again.
Where in that sequence is the nfs client umounted? Dunno, but there is a
flaw somewhere. Either kde whatever should refuse to halt knowing that
they will not be able to do so, or some script/program should be modified
apropiately. Or the halt script should nicely recover, somehow.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFGKQNvtTMYHG2NR9URAhe4AJsFoA/6FF1jahHhNNCK/Mkw6PVleACfSwnG
IRZfzMq3ckv+NFkG0zDcBKY=
=ZsKT
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
