Bug#846401: ITP: fswatch -- File change monitor that receives notifications on file or directory changes
On Thu, 1 Dec 2016 09:39:21 + Dimitri John Ledkov wrote: > systemd has native path units for inotify already. Are you packaging > this just for kfreebsd? If packaging for Linux too - why not simply > use systemd units? Good question - i'm using systemd on my systems longer that it is default in debian, we as a derivative switched in December 2013, but sometimes i set up debian machines without systemd without systemd - second i like it to have simple cli utils for several tasks - like fswatch. systemd is fine but it would be overkill in some cases.
Bug#846401: ITP: fswatch -- File change monitor that receives notifications on file or directory changes
Dimitri John Ledkov writes: > On 1 Dec 2016 00:36, "Alf Gaida" wrote: >> fswatch is a file change monitor that receives notifications when the >> contents of the specified > > systemd has native path units for inotify already. Are you packaging this > just for kfreebsd? If packaging for Linux too - why not simply use systemd > units? Your suggestion will not help when trying to deploy a solution to a heterogenous network, due to systemd's inexistent portability. Quite unlike fswatch, which promises to run on many types of kernels. - Carsten
Bug#846401: ITP: fswatch -- File change monitor that receives notifications on file or directory changes
On 1 Dec 2016 00:36, "Alf Gaida" wrote: > > Package: wnpp > Severity: wishlist > Owner: Alf Gaida > > * Package name: fswatch > Version : 1.9.96 > Upstream Author : Enrico M. Crisostomo > * URL : https://github.com/emcrisostomo/fswatch > * License : GPL-3+ > Programming Lang: C, C++ > Description : File change monitor that receives notifications on file or directory changes > > fswatch is a file change monitor that receives notifications when the contents of the specified systemd has native path units for inotify already. Are you packaging this just for kfreebsd? If packaging for Linux too - why not simply use systemd units? > files or directories are modified. fswatch implements four kinds of monitors: > * A monitor based on the File System Events API of Apple OS X. > * A monitor based on kqueue, a notification interface introduced in FreeBSD 4.1 (and supported >on most *BSD systems, including OS X). > * A monitor based on the File Events Notification API of the Solaris kernel and its derivatives. > * A monitor based on inotify, a Linux kernel subsystem that reports file system changes to applications. > * A monitor based on ReadDirectoryChangesW, a Microsoft Windows API that reports changes to a directory. > * A monitor which periodically stats the file system, saves file modification times in memory, and >manually calculates file system changes (which works anywhere stat (2) can be used). > > fswatch should build and work correctly on any system shipping either of the aforementioned APIs. >
Bug#846401: ITP: fswatch -- File change monitor that receives notifications on file or directory changes
Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name: fswatch Version : 1.9.96 Upstream Author : Enrico M. Crisostomo * URL : https://github.com/emcrisostomo/fswatch * License : GPL-3+ Programming Lang: C, C++ Description : File change monitor that receives notifications on file or directory changes fswatch is a file change monitor that receives notifications when the contents of the specified files or directories are modified. fswatch implements four kinds of monitors: * A monitor based on the File System Events API of Apple OS X. * A monitor based on kqueue, a notification interface introduced in FreeBSD 4.1 (and supported on most *BSD systems, including OS X). * A monitor based on the File Events Notification API of the Solaris kernel and its derivatives. * A monitor based on inotify, a Linux kernel subsystem that reports file system changes to applications. * A monitor based on ReadDirectoryChangesW, a Microsoft Windows API that reports changes to a directory. * A monitor which periodically stats the file system, saves file modification times in memory, and manually calculates file system changes (which works anywhere stat (2) can be used). fswatch should build and work correctly on any system shipping either of the aforementioned APIs.
