Re: [Dazuko-devel] Buggy close-modified events on Linux 2.4?

[John Ogness]

Tikka, Sami wrote:
> But the modification of the file in /tmp is weird. It results in 2 OPEN
> events and 2 CLOSE events, no CLOSE(modified) events.
> 
> Am I missing something, doing something wrong or is there a bug?

Hi,

The CLOSE(modified) has been disabled for 2.1.x. A CLOSE(modified) event
is quite complex if it is to be implemented "correctly". The way that it
was implemented in 2.0.x and earlier was very sloppy and unreliable. If
an application needs to know this information, it is best if the
application determines this itself.

This doesn't mean that the event is forever "banned", but for the moment
it is not going to be implemented.

As for the 2 OPEN and 2 CLOSE events, this probably occurs because
dup(2) is being called. This function has the same affect as an open(2)
and therefore causes additional OPEN and CLOSE events.

John Ogness

-- 
Dazuko Maintainer