The file check daemon monitors files according to rules defined in configuration files. When a file is considered stable (due to its age, presence of a flag file, etc.) then it gets copied to a new location. Rotating backups of the destination file can be made and owner, group and permissions can be specified for the destination. Some examples of where this utility has been found to be useful are: Moving files out of an incoming FTP directory in a timely manner. Moving files uploaded to a web server into directories with different user/group. This lets the administrator run the web server as a non-root user and accept uploads using web server based authentication and then move the files to a more secure area after the transfer. The details of how to determine whether a file is stable and what to do with it once it is are defined in a "Filespec" configuration file. There is a separate filespec for each file that will be monitored which means that each file can have unique behavior associated with it.
Gfarm is a distributed filesystem, generally used for large scale cluster computing. It's implemented in userland, and can be mounted by FUSE. It utilizes locality of a file to access a data node, and supports Globus GSI for Wide Area Network. Users can explicitly control file replica location on Gfarm. Gfarm can be used as an alternative storage system to HDFS for Hadoop, Samba, MPI-IO, and GridFTP. Monitoring via ZABBIX and Ganglia is also supported.
LMDBG is a collection of small tools for collecting and analyzing the logs of malloc/realloc/memalign/free function calls. Unlike many others, LMDBG does not provide any way to detect overruns of the boundaries of malloc() memory allocations, as this is not the goal. Like most other malloc debuggers, LMDBG allows detecting memory leaks and double frees. However, unlike others, LMDBG generates full stacktraces and separates the logging process from analysis, thus allowing you to analyze an application on a per-module basis.