Projects

fsniper

fsniper is a tool that monitors a given set of directories for new or modified files. Then, based on the file's type or name, it invokes a script to be run on that file. Directories are monitored using inotify, instead of simply continuously polling them for changes. Common uses include ... [More] making a single download directory for all things from a web browser and having semi-intelligent scripts figure out what to do with those files. You write the scripts yourself. [Less]

inoclam

inoclam uses inotify to watch user specified directories. When a file is created, changed or copied to one of the monitored directories, the file is virus checked with ClamAV. If a virus is detected, the file is optionally removed from the file system and the administrator is optionally notified.

lsyncd

lsyncd - Live Syncing (Mirror) DaemonDescriptionLsyncd uses rsync to synchronize local directories with a remote machine running rsyncd. Lsyncd watches multiple directories trees through inotify. The first step after adding the watches is to rsync all directories with the remote host, and then ... [More] sync single file by collecting the inotify events. So lsyncd is a light-weight live mirror solution that should be easy to install and use while blending well with your system. See lsyncd --help for detailed command line options. License: GPLv2 or any later GPL version. When to useLsyncd is designed to synchronize a local directory tree with low profile of expected changes to a remote mirror. On the receivers side rsyncd can be configured to also change the uid/gid of the file. Lsyncd is especially useful to sync data from a secure area to a not-so-secure area (e.g. as a one way connection to allow employees to publish their files to a public accessible web server). When not to use: File with active file handles (e.g. database files) Directories where many changes occur (like mail or news servers) In these cases e.g. DRBD (see http://www.linux-ha.org/DRBD) might be better for you. Comparisons:Lsyncd vs. DRBD: DRBD operates on block device level. This makes it useful for synchronizing systems that are under heavy load. Lsyncd on the other hand does not require you to change block devices and/or mount points, allows you to change uid/gid of the transferred files, separates the receiver through the one-way nature of rsync. However when using lsyncd a file change can possibly result in a full file transfer (at least for binary files) and is therefore unsuitable for databases. Also a directory rename will result in transferring the whole directory. Lsyncd vs. incron: Incron does not (yet) support recursive directory watching making it unsuitable for described needs (http://inotify.aiken.cz/?section=incron&page=about&lang=en). In fact a different approach would have been to extent incron. However, we decided to stick to the NIH principle (Not Invented Here) :-), because extending the C++ solution seemed to tedious. Lsyncd vs. FUSE: Another interesting idea is to write a daemon that provides a shadow file system through fuse. When accessing a file the data is synced to a local file as well as a remote file. With this approach inotify could be replaced. BindFS (see http://www.cs.helsinki.fi/u/partel/bindfs/) does this for local mirroring. We discarded this idea because it would affect performance of normal operations in a negative way. Lsyncd vs. cron: If you find a solution using cron to call rsync over the whole directory tree periodically after every 'X' hours/minutes/seconds more satisfying than lsyncd, please go for it ''sulking''. We don't like it! Lsyncd usage examples/usr/sbin/lsyncd /var/www/ remotehost::wwwshare/ This watches and rsycn's the local directory /var/www/ with all subdirectories and transfers them to 'remotehost' using the rsync-share 'wwwshare'. /usr/sbin/lsyncd --nodaemon --exclude-from /etc/lsycnd/exclude /var/www/ remotehost::wwwshare/ This will also rsync/watch '/var/www', but it excludes files and directories from '/etc/lsycnd/exclude'. Additionally this example lsyncd will not fork, and log to stdout/stderr instead. Some more complicated examples, tips and tricks you can find in the [HowTos] section. Source DocumentationThe only file of interest is 'lsyncd.c' which has javadoc like comments. Everything else in the tarball is packaging bushwa. DisclaimerBesides the usual disclaimer in the license, we want to specifically EMPHASIZE that NEITHER the authors NOR any organization the authors are associated with can and will hold responsible for data-loss caused by possible malfunctions of lsyncd. Especially if you run it with root privileges ;-) (we ourselves run lsyncd as www-data). [Less]

File Conveyor

File Conveyor is a daemon written in Python to detect, process and sync files. It was written by Wim Leers as part of his bachelor thesis at Hasselt University in Belgium. To allow for instantaneous detection of changes on the file system, it uses inotify on Linux and FSEvents on Mac OS X. ... [More] Files can then be processed. Processors include: -image_optimizer, capable of optimizing images without losing quality - yui_compressor, to compress CSS and JS files using the YUI Compressor - … And finally, “transporters” are used to transport files from the server the daemon is running on to the CDN. Transporters include: - FTP - Amazon S3 - Amazon CloudFront - Mosso CloudFiles [Less]

inotail

inotail is a replacement for the 'tail' program found in the base installation of every Linux/UNIX system. It makes use of the inotify infrastructure in recent versions of the Linux kernel to speed up tailing files in the follow mode (the '-f' option). Standard tail polls the file ... [More] every second by default while inotail listens to special events sent by the kernel through the inotify API to determine whether a file needs to be reread. [Less]

Getit

Getit, simplified, yet powerful download manager. Getit is a daemon to manage concurrent URL downloads with wget. It uses very simple but powerful queue mechanism to download any URL that get pasted in queue file. Queue file is a simple text file that accepts not only URLs but also download ... [More] subdirectory and download rate. Getit monitors the queue file and detects any changes that made in queue file, and determine if its necessary to terminate any download that is in progress or not, so it ignores any changes that is not related to in progress downloads. Getit is capable of detecting broken links and push those to end of the queue. Getit downloads all URLs to a temporary directory and moves those to target subdirectory after completion. --------- git clone git://github.com/armen/getit.git [Less]

openduckbill

Openduckbill is a simple command line backup tool for Linux, which is capable of monitoring the files/directories marked for backups for any changes and transferring these changes either to a local backup directory or a remote NFS exported partition or to a remote ssh server using the very common ... [More] , rsync command. As a backup tool, openduckbill can operate in any one of the modes mentioned below: Maintain an exact copy of the source at the backup destination Maintain current and previous version of the source at the backup destination Features Supports recursive and non-recursive backup of files/directories Does filesystem monitoring Openduckbill uses pyinotify for filesystem monitoring. Any directory marked for backup, will be monitored for changes, and the changes will be synced to the backup destination regularly. Three different modes of backup. Supports backup to Local directory NFS mount SSH server (using rsync over ssh) Include/exclude files/directories from backup Supports including/excluding files/directories from backup using pattern matches Supports maintaining current and previous versions of files at backup destination. In NFS backup mode, the NFS partition is auto mounted. Ability to remove files/directories which are not part of backup schedule from backup partition. (Currently this feature supported only in LOCAL and NFS backup modes.) Uses YAML based config file Easy to read and modify Uses GUI dialog box to display critical information Has built-in logging system Daemon mode and Non-daemon mode Extensive DEBUG info mode Fully client side application Minimal (or no) configuration required on server More details here [Less]

iWatch

iWatch is a realtime filesystem monitoring program. It is a tool for detecting changes in filesystem and reporting it immediately.It uses a simple config file in XML format and is based on inotify, a file change notification system in the Linux kernel.

pnotify

libpnotify is an event notification framework for monitoring files and directories. It is designed to be portable across different Unix-like kernels and currently supports Linux and BSD. The API is very similar to the inotify(7) API under Linux. libpnotify has been ported to the following ... [More] platforms: Linux 2.6 OpenBSD 4.0 FreeBSD 6.2 NetBSD 3.0 MacOS/X 10.4 [Less]

inotify-tools

inotify-tools is a C library and a set of command-line tools providing an interface to the Linux inotify file notification system.