You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
.bashrcin the example @serverfaultdoes not appear in the stats because the user monitors its home directory recursively but becausepath/.*is expanded and as a result a watch is set for all the .files underpath/(.bashrcincluded). The command used by the OP will never output file names because the watches are set for/tmpand any subdirectories therefore statistics will pertain only to/tmpand its subdirectories (i.e. you will see files have been accessed/moved/etc but it won't tell you their names)./tmp:inotifywait -m --format "%f" /tmp | grep --line-buffered ^test | xargs -L1 -I% sudo cat /tmp/% 2> /dev/null.inotifywatchoutput in the OP question: the 2createevents are there (so they are detected) but sinceinotifywatchwatches a directory (+any subdirectories) the statistics pertain only to that/those directories.man inotify:When a directory is monitored, inotify will return events for the directory itself, and for files inside the directory.Also,man inotifywatchis clear about which events are being watched: >EVENTS> ... A watched file or a file within a watched directory was accessed/closed/open/etc (means including events "which occur on a file"). Events for a file created after setting the watch on parent dir WILL be detected & reflected ininotifywatchstats (it will NOT mention for which files those events occured).