On Jan 3, 2008 11:31 AM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Jan 3, 2008 10:51 AM, Jason Chu <jason@archlinux.org> wrote:
On Wed, Jan 02, 2008 at 02:49:05PM -0600, Dan McGee wrote:
I've noticed lately that netfs always fails to shut down correctly, and I was wondering if this is just my system or if others are also noticing this. An easy way to check: sudo /etc/rc.d/netfs restart
If you see a [FAIL], you're in the same boat as me. Let me know and I'll file a bug report if more people have the same issue.
-Dan
It works for me (/etc/rc.d/netfs stop mind you) but I have a couple things different from most people probably: I use cifs and I don't mount the filesystem with the "defaults" option (ie. noauto).
Ah, does netfs only handle the 'auto' ones? Probably why I didn't notice this. I mount my nfs when I need it...
So the first command below returns 1, even though it appears it was successful. The second command returns 0, and it was also successful (the "nothing was mounted" line is a lie, as far as I can tell). I do see some weird port stuff there. I also can't find any documentation anywhere on umount return codes. [root@dublin ~]# /bin/umount -v -a -t nfs,smbfs,codafs,ncpfs,cifs,shfs,fuse,fuseblk mount: trying 192.168.1.101 prog 100005 vers 3 prot tcp port 48308 cork:/home/dmcgee umounted [root@dublin ~]# /bin/mount -v -a -t nfs,smbfs,codafs,ncpfs,cifs,shfs,fuse,fuseblk mount: trying 192.168.1.101 prog 100003 vers 3 prot tcp port 2049 mount: trying 192.168.1.101 prog 100005 vers 3 prot udp port 32775 nothing was mounted Both commands below return 0, which is interesting. Umount bug, perhaps? [root@dublin ~]# umount -v /home/dmcgee/cork mount: trying 192.168.1.101 prog 100005 vers 3 prot tcp port 48308 cork:/home/dmcgee umounted Could not find /home/dmcgee/cork in mtab [root@dublin ~]# mount -v /home/dmcgee/cork mount: trying 192.168.1.101 prog 100003 vers 3 prot tcp port 2049 mount: trying 192.168.1.101 prog 100005 vers 3 prot udp port 32775 -Dan