Re: emelfm2 pre-release

On Sat, 29 Oct 2005 07:30:37 +1000

<snip> 
> This one would have been a release, but we're still
> chasing a problem related to file-alteration-monitoring
> ("fam") by dnotify, exhibited on one tester's linux-smp
> system. He sees bogus filelist refreshing, starting when
> no-one is looking, endlessly-repeated, and it clobbers
> any useful debug-related information ...

Hi Tom.

As you know from correspondence off-list, I have an smp
box.   Just as you announced 20051028 I was in the process
of upgrading my kernel from 2.6.10 to 2.6.14 so I took the
opportunity to compile usigng USE_INOTIFY=1.  I am also on
the current gtk so I also set USE_LATEST=1.

So far I have not seen any of the constant refreshes that
plague your other smp tester - but then I was not seeing
them before the uprgrade either. Inotify seems to be working
nicely.

Because I have been carrying out several other major updates
in addition to the kernel, things have been too hectic to
carry out a really comprehensive test of the new release,
but I have used it throughout the upgrading process (often
with several instances open simultaneously because I am not
always a very tidy worker), and it has held up up well.  I
have seen a couple of lock-ups requiring a kill - but I
have not been able to reproduce and, as I have said, my
system has been in such a state of transition that the
cause may have been somewhere other than emelfm2.

One other thing is that two or three times doing an "info"
check on a symlink has produced a garbage result - just a
string of characters.  Running the old emelfm on each
occasion (with emelfm2's garbage result still onscreen),
has given the correct output.

I will post more if and when I know more.

Geoff

                
___________________________________________________________ 
To help you stay safe and secure online, we've developed the all new Yahoo! 
Security Centre. http://uk.security.yahoo.com


-- 
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: