Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for other inotify events #2

Open
AdUser opened this issue Aug 23, 2011 · 1 comment
Open

Support for other inotify events #2

AdUser opened this issue Aug 23, 2011 · 1 comment

Comments

@AdUser
Copy link

AdUser commented Aug 23, 2011

I need more advanced event tracking (not only predefined CLOSE_WRITE,CREATE,MOVED_TO and DELETE on files only). Which best way to do this? By exporting event to handler, like filename? By limiting handlers to listen only for certain events? Or some other way?

@daf
Copy link
Member

daf commented Sep 15, 2011

We've debated this - the goal of fsniper was always a more specific use case, rather than a general framework like incron (http://inotify.aiken.cz/?section=incron&page=about&lang=en) for instance.

I wouldn't mind adding more inotify related events but i do not want to make users specify the default use of fsniper (closed for writing) - it makes the config worse than it already is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants