Ressource leak issue about pyinotify

[seb-m]

Pyinotify binds inotify system calls so all the sensible stuff is done in the kernel, it's unlikely that Pyinotify could leak anything. In any case the number of watches you try to set seems a little bit high I think.

[hjdr4]

Hi,

Thanks for your answer. I had another pynotify based job (a pywatcher one) from my company monitoring system. Once I realized that, I restarted it and I could run pyinotify again normally without rebooting the host. Still don't know how such interference can happen but it works. I would have another question : since watching a tree requires recursive registering of all directories, this can take ages on large trees (it took about 1 hour to watch my 300000 folders). What is the Linux way to watch such a tree in 2012 ? (I could ask the same question if I wanted to watch my entire system). You know, 20 TB is just a bunch of disks.

Regards

[seb-m]

Indeed it is painful. I seriously don't know if there is a better way of doing it, even now, but I might be a bit a rusty on these questions so don't take my answer for definitive, it might very well be a more adapted and newer mechanism, I'm just not following closely these areas anymore.