Root, via /etc/incron.d/foo, received an IN_IGNORED event when monitoring file foo when emacs (I believe) deleted foo~ in a second editing session after, in an initial editing session, changing the name of foo to foo~ and leaving it as a backup file.
The identical incrontab entry in the user's incrontab
This bug report is a copy of https://bugs.debian.org/592692
[Karl O. Pinc]
Root, via /etc/incron.d/foo, received an IN_IGNORED event when monitoring file foo when emacs (I believe) deleted foo~ in a second editing session after, in an initial editing session, changing the name of foo to foo~ and leaving it as a backup file.
The identical incrontab entry in the user's incrontab
/home/kop/tmp/incron/foo IN_MODIFY,IN_ATTRIB,IN_CLOSE_WRITE logger -t rootincrontab "Received event $%"
received no such event. (AFAICT)
In any case IN_IGNORED is not documented in the incrontab(5) man page.