Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
For anyone having the same problem, here is the workaround I am using. We assume your nfs homes are mounted in /home/nfs. 1) Create a file named /etc/init.d/killnfs, with the following content: #!/bin/sh # # Script to kill any remaining processes in /home/nfs, and unmount it. # It should be run after gdm stops. # /bin/fuser -km /home/nfs umount /home/nfs 2) Save it, and then make it executable by running: chmod 755 /etc/init.d/killnfs 3) Set it to execute on shutown, after gdm stops, by running: update-rc.d killnfs stop 02 0 6 . Best regards.
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
In the meantime, is there any way I can reduce this 30 secs timeout (i.e., changing any config flag or something)? Thank you very much.
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
Le mercredi 01 octobre 2008 à 10:42 +, Juan Miguel Corral a écrit : In the meantime, is there any way I can reduce this 30 secs timeout (i.e., changing any config flag or something)? No, it is hardcoded. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
This should not happen, since gconfd-2 does not keep any open file in /home. Could you check what files are open at the time the umount is blocking? Confirmed. The file is ~/.gconfd/saved_state. gconfd-2 keeps it open for about 30 seconds after the session is closed. I have tried, as a workaround, to add a script in runlevels 0 and 6, that executes the first, and reports every proccess accessing the nfs-homes filesystem an then kills it. This is the output: USERPID ACCESS COMMAND /home/cfs: jmcorral 4201 F gconfd-2 With this script killing the gconfd-2 proccess, shutdown sequence proceeds normally: no errors, and the computer powers off.
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
Le mardi 30 septembre 2008 à 11:46 +, Juan Miguel Corral a écrit : This should not happen, since gconfd-2 does not keep any open file in /home. Could you check what files are open at the time the umount is blocking? Confirmed. The file is ~/.gconfd/saved_state. gconfd-2 keeps it open for about 30 seconds after the session is closed. Ah, indeed the log file is kept open for 30 seconds after each time something is written to it. Thinking about it, it is strange that, even while only local locks are used, the log file is put in /home. It should land in the same directory as the lock, which means in /tmp/gconfd-$user. It will also avoid a lot of unnecessary writes over the network for NFS homes. Do other readers agree with that solution? -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
On Tue, Sep 30, 2008, Josselin Mouette wrote: Confirmed. The file is ~/.gconfd/saved_state. gconfd-2 keeps it open for about 30 seconds after the session is closed. Thinking about it, it is strange that, even while only local locks are used, the log file is put in /home. It should land in the same directory as the lock, which means in /tmp/gconfd-$user. It will also avoid a lot of unnecessary writes over the network for NFS homes. This solution is probably not suitable for 2.24: 2.23.2 == Features - stop using /tmp for the IOR, instead use the DBus session bus (Ray Strode) I grepped the source for /tmp, and only the testsuite seems to use that nowadays. Sadly, gconfd/saved_state is still used for similar logging which is used to restore listeners when gconfd restarts (AIUI). The log files is used in two ways: continuous logging happens all the time, and will be used if the process dies badly, and if the process gets the time to shutdown decently or for some signals, it will save its state to a new file, and overwrite the logfile with this state before exiting. I'd say that the open file, the continuous write to a real file (which might spinup the hard disk IIUC or cause network IO as you point out) is completely an obsolete use case, and we should simply rely on the latter part of the saving process. Perhaps we can propose that upstream. -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
Le mardi 30 septembre 2008 à 21:26 +0200, Loïc Minier a écrit : Sadly, gconfd/saved_state is still used for similar logging which is used to restore listeners when gconfd restarts (AIUI). The log files is used in two ways: continuous logging happens all the time, and will be used if the process dies badly, and if the process gets the time to shutdown decently or for some signals, it will save its state to a new file, and overwrite the logfile with this state before exiting. I'd say that the open file, the continuous write to a real file (which might spinup the hard disk IIUC or cause network IO as you point out) is completely an obsolete use case, and we should simply rely on the latter part of the saving process. Perhaps we can propose that upstream. Add to that the fact this feature is here for the case where gconfd crashes unexpectedly, and that it is very stable nowadays, so that makes it quite useless. I’ll propose to remove it to upstream. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
Package: gconf2 Version: 2.22.0-1 Severity: important From http://www.gnome.org/projects/gconf: quote gconfd keeps me from unmounting my home directory, how can I get it to exit? It should exit a couple of minutes after the last application using GConf has exited. You could put a gconftool --shutdown in your .logout script or the like, if you want it to exit sooner. /quote Gconfd-2 will stay alive for about 30 secs after user has logged out. Well, if you have nfs4 mounted homes, then debian will hang indefinitely when you shutdown via gnome, since it will be unable to unmount the filesystem because gconfd-2 is using it. I am experiencing this on my network. I think the best solution is to make gconfd-2 be shut down when user logs out. I have tried putting the line gconftool-2 --shutdown on /etc/gdm/PostSession/Default, but doesn't work. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gconf2 depends on: ii gconf2-common 2.22.0-1 GNOME configuration database syste ii libc6 2.7-13GNU C Library: Shared libraries ii libgconf2-42.22.0-1 GNOME configuration database syste ii libglib2.0-0 2.16.5-1 The GLib library of C routines ii libxml22.6.32.dfsg-4 GNOME XML library ii psmisc 22.6-1Utilities that use the proc filesy ii python 2.5.2-2 An interactive high-level object-o Versions of packages gconf2 recommends: ii libgtk2.0-0 2.12.11-3 The GTK+ graphical user interface gconf2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
reassign 500430 gnome-session severity 500430 normal retitle 500430 Could try to shutdown gconf after logout stop On Sun, Sep 28, 2008, Juan Miguel Corral Cano wrote: Gconfd-2 will stay alive for about 30 secs after user has logged out. Well, if you have nfs4 mounted homes, then debian will hang indefinitely when you shutdown via gnome, since it will be unable to unmount the filesystem because gconfd-2 is using it. I am experiencing this on my network. I think the best solution is to make gconfd-2 be shut down when user logs out. I have tried putting the line gconftool-2 --shutdown on /etc/gdm/PostSession/Default, but doesn't work. What software is responsible for unmounting on your system? is it PAM? I would guess this software needs to wait longer for processes to shutdown, such as gconf. I think gnome-session could try to shutdown gconf, but I'm not sure how easy that is with the WM also using gconf. -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
Le dimanche 28 septembre 2008 à 11:42 +0200, Loïc Minier a écrit : reassign 500430 gnome-session severity 500430 normal retitle 500430 Could try to shutdown gconf after logout stop On Sun, Sep 28, 2008, Juan Miguel Corral Cano wrote: Gconfd-2 will stay alive for about 30 secs after user has logged out. Well, if you have nfs4 mounted homes, then debian will hang indefinitely when you shutdown via gnome, since it will be unable to unmount the filesystem because gconfd-2 is using it. I am experiencing this on my network. This should not happen, since gconfd-2 does not keep any open file in /home. Could you check what files are open at the time the umount is blocking? I think gnome-session could try to shutdown gconf, but I'm not sure how easy that is with the WM also using gconf. It could, and it will probably do that when gconf finally uses dbus. However that should not be necessary for unmounting partitions. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
