Skip to content
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.

inotify/IN_MOVED_TO #25

Closed
cpisto opened this issue Nov 1, 2012 · 3 comments
Closed

inotify/IN_MOVED_TO #25

cpisto opened this issue Nov 1, 2012 · 3 comments

Comments

@cpisto
Copy link

cpisto commented Nov 1, 2012

Is there a particular reason IN_MOVED_TO isn't supported for rename events in the inotify/linux backend? Without it, watching for files being moved into a directory is not possible..

@howeyc
Copy link
Owner

howeyc commented Nov 1, 2012

I could probably add that in, I'd have to see how it compares to behavior
on Windows and OSX/BSD. I would assume such a situation to behave similar
to a CREATE event, but I'll take a look and do some testing to find out.

On 31 October 2012 23:02, Cody Pisto notifications@github.com wrote:

Is there a particular reason IN_MOVED_TO isn't supported for rename events
in the inotify/linux backend? Without it, watching for files being moved
into a directory is not possible..


Reply to this email directly or view it on GitHubhttps://github.com//issues/25.

@cpisto
Copy link
Author

cpisto commented Nov 1, 2012

I agree, the way the fsnotify API is structured now, it would fit best with being a CREATE event.

@howeyc
Copy link
Owner

howeyc commented Nov 3, 2012

I added IN_MOVED_TO which will generate a CREATE event.

@howeyc howeyc closed this as completed Nov 3, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants