and you add a watch for dir, it gets watchID 1. Actions that happen to fileA or subdir itself are raised for watchID 1 as expected. Events that happen to fileB are raised for watchID 2 and are thus missed by client code looking for events related to the ID it was given. Considering this doesn't happen on any platform other than Linux, I presume it to be a bug?
If you have a directory structure like this:
and you add a watch for
dir
, it gets watchID 1. Actions that happen tofileA
orsubdir
itself are raised for watchID 1 as expected. Events that happen tofileB
are raised for watchID 2 and are thus missed by client code looking for events related to the ID it was given. Considering this doesn't happen on any platform other than Linux, I presume it to be a bug?Tested on CentOS 7 and CentOS 9