after a user logout gconfd-2 still using ~/.gconfd/saved_state Reproducible: Always Actual Results: date; who;lsof | grep home Fri Nov 14 22:13:15 CET 2008 root pts/0 Nov 14 21:40 (uzzmaster.uzz.local) michele pts/1 Nov 14 22:13 (uzzmaster.uzz.local) gconfd-2 5137 michele 15w REG 0,16 633 95165 /home/michele/.gconfd/saved_state bash 5147 michele cwd DIR 0,16 3848 1093 /home/michele ------------------------- date; who;lsof | grep home Fri Nov 14 22:13:19 CET 2008 root pts/0 Nov 14 21:40 (uzzmaster.uzz.local) gconfd-2 5137 michele 15w REG 0,16 633 95165 /home/michele/.gconfd/saved_state ------------------- date; who;lsof | grep home Fri Nov 14 22:13:41 CET 2008 root pts/0 Nov 14 21:40 (uzzmaster.uzz.local) gconfd-2 5137 michele 15w REG 0,16 633 95165 /home/michele/.gconfd/saved_state speriment ~ # date; who;lsof | grep home Fri Nov 14 22:13:46 CET 2008 root pts/0 Nov 14 21:40 (uzzmaster.uzz.local) Expected Results: gconfd-2 will be little faster for unlock ~/.gconfd/saved_state from client mounting /home via nfsv4. If from a client a user will turn off the computer, /etc/init.d/nfsmount stop will exit with error because it cannot umount /home. after nfsmount will exit with error all other daemon will not stop because nfsmount still running. i'm uning openrc-2.5 Please add in CC of this bug also nfs dev group.
this is perfectly normal, it is stated in upstream configuration that using gconf over nfs will cause this problem because gconf waits for all clients to have exited and then times out before dying, this can take a few seconds. The solution is to call gconftool2 --shutdown on session shutdown. This can be added to PostSession scripts in gdm if you are using it. Since this is a configuration issue and not a bug, I'm closing this as invalid.
thanks, i didn't know about PostSession. but with sshd_config values of X11Forwarding yes i think gconfd start a session without gdm. i didn't write before, but in my example i was login from ssh.
