Bug#695765: ITP: fsniper -- daemon to run scripts based on changes in files monitored by inotify
Package: wnpp Severity: wishlist Owner: Alex 'AdUser' Z ad_u...@lavabit.com * Package name: fsniper Version : 1.3.1 Upstream Author : Andrew Yates, David A. Foster * URL : https://github.com/l3ib/fsniper * License : GPL-3+ Programming Lang: C Description : daemon to run scripts based on changes in files monitored by inotify fsniper is a lightweight daemon, that watches given set fo files and/or directories with inotify, and executes commands on inotify events. . This may be useful for seting up self-managed upload, temp or spool dirs. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121212125005.28143.3844.report...@balthasar.home.lan
Re: Bug#695765: ITP: fsniper -- daemon to run scripts based on changes in files monitored by inotify
Hi, On 12.12.2012 13:50, Alex 'AdUser' Z wrote: fsniper is a lightweight daemon, that watches given set fo files and/or directories with inotify, and executes commands on inotify events. . This may be useful for seting up self-managed upload, temp or spool dirs. How is this better/different to incron(d) [1]? [1] http://packages.debian.org/sid/incron -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Re: Bug#695765: ITP: fsniper -- daemon to run scripts based on changes in files monitored by inotify
Arno Töll wrote 2012-12-13 00:19: Hi, On 12.12.2012 13:50, Alex 'AdUser' Z wrote: fsniper is a lightweight daemon, that watches given set fo files and/or directories with inotify, and executes commands on inotify events. . This may be useful for seting up self-managed upload, temp or spool dirs. How is this better/different to incron(d) [1]? [1] http://packages.debian.org/sid/incron Well, for me, killer features was (compared to incrond): * chain handlers (one event may have multiple handlers, which executes untill one returns zero code) * built-in filtering support: * file extension * mime-type * filename regexps * automatically watch newly created directories * written in pure c (instead c++) All this, except last two may be implemented inside event handler, but I'm quite lazy to reinvent wheels. :-) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e00709d3e232fd9465aeeb875beb5...@lavabit.com
Re: Bug#695765: ITP: fsniper -- daemon to run scripts based on changes in files monitored by inotify
Arno Töll wrote (12 Dec 2012 13:19:14 GMT) : How is this better/different to incron(d) [1]? We also have inoticoming to deal with the simplest case. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/85r4mv4bav@boum.org
Re: Bug#695765: ITP: fsniper -- daemon to run scripts based on changes in files monitored by inotify
On 12/12/2012 21:42, Alex Z wrote: Well, for me, killer features was (compared to incrond): * chain handlers (one event may have multiple handlers, which executes untill one returns zero code) * built-in filtering support: * file extension * mime-type * filename regexps * automatically watch newly created directories * written in pure c (instead c++) I'm curious. Why is written in pure c a killer feature? -- Kind regards, Loong Jin signature.asc Description: OpenPGP digital signature
