Date: Tue, 5 May 2009 00:32:16 +0200 From: "barbara" <barbara.xxx1975@libero.it> To: "freebsd-gnome" <freebsd-gnome@freebsd.org> Subject: Re: Nauilusgamin stops showing directory changes Message-ID: <KJ559S$9FC6B135B8DAEDAA42A0A92CAA8EFA31@libero.it>
next in thread | raw e-mail | index | archive | help
> > Am Donnerstag, den 30.04.2009, 02:14 -0400 schrieb Joe Marcus Clarke:= > > > On Wed, 2009-04-29 at 21:29 -0400, Jason Reid wrote: > > > > Hello, > > > > > > > > >From time to time Nautilus will not keep up with directories as = the > > > > files change. I cannot pinpoint the exact cause, but I can, for e= xample, > > > > "touch newfile" in a directory or on my Desktop, and Nautilus wil= l not > > > > show it until I open a Nautilus window to that directory/desktop = and > > > > click View -> Reload. > > > > > > > > Filesystem polling works fine after a reboot. Right now I have be= en up > > > > for 4 days and just noticed, but it's stopped working as quickly = as an > > > > hour after boot. This is not a new problem with 2.26 and is somet= hing > > > > I've experienced since at least 2.20. My system is FreeBSD 7.1-p4= i386 > > > > using a ZFS disk, but I've seen the same problem on the same comp= uter > > > > under an old installation using UFS. > > > > > > > > Some Googling reveals that Nautilus uses devel/gamin to poll chan= ges > > > > which in turn uses kqueue by default. The port has a compile-time= option > > > > for GAM_POLLER that I do not have enabled. Konqueror, however has= never > > > > exhibited this problem. > > > > > > > > The closest bug report I was able to find was > > > > https://bugzilla.redhat.com/show_bug.cgi?id=3D130859 from 2004 wh= ich I > > > > don't believe is applicable. It discusses gamin 0.0.x, and I use > > > > 0.1.10_1. > > > > > > > > My kern.maxfiles is 25000. kern.openfiles reports 10735, and "fst= at | > > > > grep gam_server | wc -l" reports 8890. > > > > > > I cannot reproduce. I've been up for over 10 days. Make sure that= > > > Nautilus is looking at a real path, and not a symlink. Gamin does = not > > > report changes on symlinks in line with the FAM spec. > > > > > I have seen the problem Jason describes quite often with older versio= ns > > of nautilus: for example when you use a different file manager like > > midnight-commander or thunar or when you log in remotely via ftp. > > I tried all these methods with nautilus-2.26.2 > > ^ > > and couldn't reproduce them either. > > > > Greetings > > > > Uli. > > > I rebooted my pc yesterday night, and this morning it was not working a= gain. > I can see nautilius not refreshing after adding/removing files/director= ies from a terminal. It just works manually. Yesterday it was working so = something happened. > > And also > [bar@satanasso:~]$ sudo umount /mnt/data/ > umount: unmount of /mnt/data failed: Device busy > [bar@satanasso:~]$ fstat | grep data > bar gam_server 1197 4884 /mnt/data 2 drwxr-xr-x 512 r > [bar@satanasso:~]$ ps axuc | grep gam_server > bar 1197 0.0 0.2 20908 3580 ?? S 10:28PM 0:57.24 gam_= server > root 72732 0.0 0.1 19884 2684 ?? I 11:27PM 0:00.01 gam_= server > > But now I've found that after: > [bar@satanasso:~]$ pkill -s HUP nautilus > I finally can > [bar@satanasso:~]$ sudo umount /mnt/data/ > > > [bar@satanasso:~]$ pkg_info -Ix gamin nautilus-2 > gamin-0.1.10_1 A file and directory monitoring system > nautilus-2.26.2_1 File manager for the GNOME desktop > Last patch for gamin seems to have fixed the problem with umount. Really really thanks for that!!! Anyway I'm still experiencing the behaviour described by Jason (nautilus = stop refreshing). I don't know what it's triggering that and if that could be related, but = I noticed that it often happens after leaving a nautilus window opened on= a directory of a mounted disk (let's call it /mnt/disk1) for many hours,= tipically whole night. I do that often when I leave the pc running for m= any hours (more then 1 day), so I don't know if it would happen anyway af= ter a long uptime for a desktop pc. What's strange is that yesterday, /mnt/disk1 was not refreshing and the s= ame for dirs in /usr. Then I mounted another device under /mnt/disk2 and = it was working as espected with that one. Sorry, I can't say more than that, I hope this could help you in diagnosi= ng the problem. I know it's not so easy to reproduce. If you have any idea about what I could do to help, please ask. Regards Barbara
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KJ559S$9FC6B135B8DAEDAA42A0A92CAA8EFA31>