On Wed, 3 Oct 2001, Alex Larsson wrote:
> This happened for us in Nautilus. When saving a file fam sent an event for
> the truncate, leading to Nautilus updating it's data, showing a file size
> of zero. Then when the changes that wrote to the file arrived they weren't
> detected as changes by fam, because they were in the same second. This
> caused Nautilus to keep displaying 0 bytes for the file.
Too bad the event isn't sent at the end of the second, not when
the first change is seen. That is, the semantics of the event
should be "1 or more changes seen in last second", not "1 or
more changes will happen in the next second".
I won't rest till it's the best ...
Manager, Linux Scalability
Paul Jackson <pj@xxxxxxx> 1.650.933.1373
--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx
|