No Events are Triggered by Watcher in CentOS 6.4

[michael-martin-al]

I was using exactly the same code in CentOS 5 and it worked flawlessly. Now, I moved my application to CentOS 6.4 and no events are being triggered by my watcher.

[michael-martin-al]

I went back and tested on CentOS 5. The problem is not related to OS version. When I put my application on the new server, I recompiled from source and Go must have picked up the latest version of fsnotify. Now, my watcher triggers no events at all on CentOS 5 or 6. It was working previously. No other code has changed.

[howeyc]

I probably messed something up when adding the Select code. Seems to work
for me though.

You can go back to commit c23ce3f until I
can figure it out. I'll try to get to it as soon as possible.

Also, any chance this is 32 bit?
On Jun 19, 2013 12:35 PM, "michael-martin-al" notifications@github.com
wrote:

I went back and tested on CentOS 5. The problem is not related to OS
version. When I put my application on the new server, I recompiled from
source and Go must have picked up the latest version of fsnotify. Now, my
watcher triggers no events at all on CentOS 5 or 6. It was working
previously. No other code has changed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52#issuecomment-19700037
.

[michael-martin-al]

I will try the commit you suggested, and the server is 64-bit.

[ohlol]

#51

[nathany]

@michael-martin-al I'm not sure if this issue still exists?

I'm curious if running the fsnotify test suite on CentOS results in failures?

• If the tests fail, we should consider adding a CentOS box to our Vagrantfile for testing. Currently it only has Ubuntu and FreeBSD.
• If the tests pass, we'll probably need to start with a failing test case to cover this issue.

Also, a git bisect would help identify the exact commit where the issue appeared.

[nathany]

@michael-martin-al If this is still an issue with the latest code (go get -u github.com/howeyc/fsnotify) would you mind opening the issue over at https://code.google.com/p/go/issues/list?q=fsnotify (for go.exp/fsnotify)? We are currently transitioning development there.