On Sat, 4 Aug 2012, the wise Kevin Oberman wrote:
Do you have comms/usbmuxd installed? I seem to recall an issue where it
could cause one of the Gnome related processes to go to 100%. I just
don't recall if it was gamin, but I removed the usbmuxd port and those
dependent on it, all of which
On Sat, 4 Aug 2012, the wise Kevin Oberman wrote:
Finally found this one.
Gamin needs some files that aren't there by default:
~/.gaminrc and /usr/local/etc/gamin/gaminrc.
In these files you need to put two lines:
fsset ufs poll 10
fsset zfs poll 10
to prevent gam_server from polling
The file /usr/local/etc/gamin/gaminrc is not always necessary, and setting
the time interval to 10 seconds may cause gamin to function improperly
according to my experience. Hope someone could dig into the problem and
find a solution.
B.R.
HU Dong
On Sat, Aug 4, 2012 at 10:48 PM, Marco
Hi,
Every time when Gnome (2.32) starts, gam_server is going to 100% cpu
usage.
Does anyone knows why this can happen?
I use FreeBSD 9-STABLE on i386.
Regards,
Marco
--
Oh I'm just a typical American boy
From a typical American town.
I believe in God and Senator Dodd
And keeping old
$ cat ~/.gaminrc
fsset ufs kernel 1
fsset zfs kernel 1
It tells gamin to update every 1 second.
On Sat, Aug 4, 2012 at 5:35 AM, Marco Beishuizen mb...@xs4all.nl wrote:
Hi,
Every time when Gnome (2.32) starts, gam_server is going to 100% cpu usage.
Does anyone knows why this can happen?
I
On Sat, 4 Aug 2012, the wise HU Dong wrote:
$ cat ~/.gaminrc
fsset ufs kernel 1
fsset zfs kernel 1
It tells gamin to update every 1 second.
Sorry, didn't help. Gam_server still running at 100%.
--
In war, truth is the first casualty.
-- U Thant
It did help me. Maybe you can increase the time interval.
Anyway, I think this is a common problem that the port maintainer should
consider fixing.
On Sat, Aug 4, 2012 at 8:44 AM, Marco Beishuizen mb...@xs4all.nl wrote:
On Sat, 4 Aug 2012, the wise HU Dong wrote:
$ cat ~/.gaminrc
fsset ufs
On Fri, Aug 3, 2012 at 6:00 PM, HU Dong itechb...@gmail.com wrote:
It did help me. Maybe you can increase the time interval.
Anyway, I think this is a common problem that the port maintainer should
consider fixing.
On Sat, Aug 4, 2012 at 8:44 AM, Marco Beishuizen mb...@xs4all.nl wrote:
On
