You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HI! The current behavior of inotifywait is to return events in realtime, as soon as they happen. This is interesting, but some daemons might require a compilation of events during a certain period.
For instance, below is a script to return unique events every 5 seconds:
As seen, it requires quite a few steps to create a FIFO and handling of the background process. Also the operations of sort | uniq can be CPU intensive if there are many events accumulated.
IMHO, it would be convenient to have an option in inotifywait to receive the timeframe to return events
The text was updated successfully, but these errors were encountered:
HI! The current behavior of
inotifywait
is to return events in realtime, as soon as they happen. This is interesting, but some daemons might require a compilation of events during a certain period.For instance, below is a script to return unique events every 5 seconds:
As seen, it requires quite a few steps to create a FIFO and handling of the background process. Also the operations of
sort | uniq
can be CPU intensive if there are many events accumulated.IMHO, it would be convenient to have an option in
inotifywait
to receive the timeframe to return eventsThe text was updated successfully, but these errors were encountered: