Re: Additional Pre-release Comments (GAMIN?)

> However, did notice two (2) repeated strange events since activating
> latest pre-release. Scenario is:
> 
> 1) typically start emelfm2 and leave active-minimized on one of my 
> workplaces in Xfce 4.2.2, since I utilize it regularly in my sessions
> 2) thus, emelfm2 is usually always active, and my system is always on
> and up-time is measured in days-weeks..
> 3) last night after about 10 hours activation, noticed a 'race'
> condition with CPU utilization at 49% (SMP system), TOP showed:
>       - X at 48% and emelfm2 at 1%
Probably a lot of filelist refreshing.

> 4) after selective app termination (Firefox, OOo, Kontact, etc.)
> condition ended immediately upon emelfm2 termination
> 5) started emelfm2 again- no problems until this evening; no
> intervening: reboots, session termination, or X restarts Same "race"
> condition with same TOP results. Again, "race" condition ceased
> immediately upon emelfm2 termination
> 
> Conjectures:
> a) initially installed pre-release with no MAKE options whatsoever.
> b) after some research on FAM, GAMIN, etc.- I noted that Mandriva for
> LE 2005 formally dropped FAM for GAMIN..
> c) re-installed pre-release now with MAKE option 'USE_GAMIN=1'
> 
> At this time will wait to see if if the CPU "race" condition
> re-occurs. Your comments-insights are welcomed.
USE_GAMIN=1 will turn off e2's own dnotify usage. It's a while since I
checked how mandriva's gamin is built, but IIRC it used inotify if
possible (without checking version compatibility), otherwise dnotify.
e2's approach to using the kernel mechanisms is similar to gamin's,
though less-complicated and more-comprehensive.

To help diagnose the problem, if you build e2 with DEBUG=1 and run from
a terminal, you'll see various messages, including some related to the
alteration-monitor. Those should provide more clues about what is
needed.

Access-time changes are captured more reliably in e2. When the problem
occurred, was either of the displayed directories being accessed a lot?

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: