Bug#500430: gconf2: gconfd-2 not shutting down after user's logout
joss at debian.org
Tue Sep 30 14:02:12 UTC 2008
Le mardi 30 septembre 2008 à 11:46 +0000, 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Ceci est une partie de message
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20080930/bd132b82/attachment.pgp
More information about the pkg-gnome-maintainers