The event delete_self with inotyfywait never occur
Bug #702884 reported by
Anders Wallenquist
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| inotify-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: inotify-tools
Using inotifywait waiting for a lock-file will wait for ever.
Window one:
$ inotifywait -e delete_self /tmp/foo
Setting up watches.
Watches established.
Window two:
aw@server1:~$ touch /tmp/foo # has to be done before starting inotifywait in window one
aw@server1:~$ rm /tmp/foo
(nothing happens, inotify will hang for ever)
=====
The same thing using event delete:
aw@server1:/tmp$ inotifywait -e delete /tmp
Setting up watches.
Watches established.
/tmp/ DELETE foo
The event fires
| Changed in inotify-tools (Ubuntu): | |
| status: | New → Fix Released |
Revision history for this message
| Eriberto (eriberto) wrote | #1 |
To post a comment you must log in.
Hi Anders,
Thanks for your message. I am the maintainer of inotify-tools in Debian.
Today I did several tests in Debian Sid, using your version (inotify-
# inotifywait -e delete_self /tmp/foo
Setting up watches.
Watches established.
/tmp/foo DELETE_SELF
# inotifywait -e delete /tmp
Setting up watches.
Watches established.
/tmp/ DELETE foo
Considering other tests, I am convinced that the problem occurred in kernel API or other environment control. So, I am closing this bug. Feel free to reopen if needed.
Regards,
Eriberto