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
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.
`.
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.
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 th
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 lan
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
> 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 wo
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
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 ha
Package: gconf2
Version: 2.22.0-1
Severity: important
>From http://www.gnome.org/projects/gconf:
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 --shut
10 matches
Mail list logo
