[vmchecker-dev] shall we use a newer version of pyinotify?

[Alexandru Moșoi]

ok, checking the sources [1] daemonize should solve [0]. go on, check
it on a separate branch. if you end up writing too much code please
also look into a related issue [2]

[0] http://github.com/vmchecker/vmchecker/issues#issue/2
[1] http://git.dbzteam.org/?p=pyinotify.git;a=blob;f=pyinotify.py;h=3331c5d70987152634c97f875eeb5e3a01768c74;hb=HEAD#l1017
[2] http://github.com/vmchecker/vmchecker/issues#issue/4

2009/4/26 Lucian Adrian Grijincu <lucian.grijincu at gmail.com>:
> On Sun, Apr 26, 2009 at 6:46 PM, Alexandru Moșoi <brtzsnr at gmail.com> wrote:
>> Could you explain what's so special about that example?
>
> Sorry I It can daemonize the application (when entering .loop()).
> I don't have time to tinker with it, and pyinotify documentation sucks
> (not that ours is any better).
>
> --
>  .
> ..: Lucian
> _______________________________________________
> vmchecker-dev mailing list
> vmchecker-dev at lists.rosedu.org
> http://lists.rosedu.org/cgi-bin/mailman/listinfo/vmchecker-dev
>



-- 
Alexandru Moșoi
http://alexandru.mosoi.googlepages.com

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html