umount and RPC errors during reboot
From: news (news_at_giganews.com)
Date: 12/22/03
- Next message: Bjorn: "Re: Linux as Ethernet to serial bridge"
- Previous message: Bit Twister: "Re: How to serve atomic time to windows comptuters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 22 Dec 2003 08:07:00 -0500
I'm running two systems. First my RH9 server which is hosting all my network
accounts and second my RH9 client. The host server exports all the network
account from /export/home. The client is mounting the accounts to /home
through the /etc/fstab. I have all the necessary protocols running on each
machine, which includes (nfs, netfs, nfslock, portmap, and autofs for some
local mounting). Everything is working fine at boot-up and during all
desktop sessions. No problems sharing files, reading and or writing through
NFS.
Here's the rub. Two applications, esd and evolution leave processes running
when I exit the desktop on the client machine. When I reboot the client
umount hangs in the /home mount point complaining that the device is busy.
After the umount attempts time out I receive an RPC error 101 message. This
too times out and then the machine reboots.
The only solution I have so far was to uninstall esd (esound) and use a
different email client in place of evolution. However, I rather get some
help on trying to figure out why these processes aren't being killed after
exiting the GNOME desktop and why the umount command is failing. Also,
shouldn't there be a step in the shutdown scripts to kill any processes that
has access in the NFS devices?
-- kd
- Next message: Bjorn: "Re: Linux as Ethernet to serial bridge"
- Previous message: Bit Twister: "Re: How to serve atomic time to windows comptuters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|