Vladimir Kondratyev
Vladimir Kondratyev
> but fsnotifier still dies sometimes I quickly glanced over fsnotifier code and see at least one issue which can trigger SIGSEGV. fsnotifier misses support for partial inotify event reads...
> I fixed it by adding the SOCK_NONBLOCK option to socketpair. I'm not sure if this a proper fix. Let me know if this is ok. You are going the...
I wrote some code and put it in my git repo: https://github.com/wulf7/libinotify-kqueue but it need some testing before pull-request
I forcepushed slightly better variant to https://github.com/wulf7/libinotify-kqueue just now.
Tnx, guys for cooperation I`ve made a pull request https://github.com/dmatveev/libinotify-kqueue/pull/35
To Tobias. I have not looked in fsnotifier code but if you want to remove all watches from inotify instance, the simplest (and in many cases the best) way to...
> Aside from the expected IN_OPEN, IN_CLOSE_WRITE and IN_CLOSE_NOWRITE failures what am I missing here to get all the tests passing? Kernel should be patched to pass all the tests...
> except the last error: "watch id is -1, errno set to EACCES when starting watching a file without read access". But I cant reproduce this error in 10.2 running...
> > Are you tried to run tests as root? > > Yes, exactly. Tried this on EL6.4 just now an found that Linux root is able to open files...
There are no unexpected failures now. P.S. Thanks again for report and plz dont close this issue as it reveals a false-positive in test suite