Date: Thu, 14 Dec 2006 01:18:09 +0100 From: Bastiaan Welmers <bastiaan@welmers.net> To: Bartosz Fabianowski <freebsd@chillt.de> Cc: freebsd-questions@freebsd.org, kde-freebsd@freebsd.kde.org Subject: Re: [kde-freebsd] gamin/fam issues with KDE Message-ID: <20061214001809.GZ873@routeduvel.rembrandtkd.welmers.net> In-Reply-To: <45809593.5000902@chillt.de> References: <20061213231719.GY873@routeduvel.rembrandtkd.welmers.net> <45809593.5000902@chillt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 14, 2006 at 12:06:43AM +0000, Bartosz Fabianowski wrote: > Just a quick "me too". I have been seeing the exact same behavior ever > since gamin was shoved down our throats as a better replacement for fam. > But since nobody else complained, I figured it was just my system. When building from ports it's quite easy to change back to fam, just put WITH_FAM_SYSTEM=fam into /etc/make.conf For existing systems/binary installed systems, you can just pkg_delete -f gamin* and install fam instead, so gamin libraries wil be replaced by the fam ones, it works well to me. One nasty thing is that when afterwards installing a package requiring gamin, it will fail with errors. To prevent this you could just "fake" the pkg db that gamin is installed however actually fam libraries are installed. > Whatever gamin is doing, it is not showing up in lsof, but the file > system is still busy. I did try tweaking my ~/.gaminrc to switch to > polling for the mount points in question, but this didn't help. Oddly > enough, sometimes, maybe one time out of ten, gamin will not exhibit > this strange behavior. It will just let me unmount without any problems. Maybe because you just unmount on exactly the right moment, when gamin is not occupying the file system? Or just all windows and processes are closed cleanly. /Bastiaan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061214001809.GZ873>