Requires Linux 3.15+ and a filesystem that supports the FALLOC_FL_COLLAPSE_RANGE flag for fallocate. This is currently ext4 and XFS. Hopefully more in the future...
./curtail [-s size] <output file>
Options:
-verbose enable all debug output (on stderr)
-quiet disable all non-error output (on stderr)
-size Maximum size of the output file (ie. 8192, 64K, 10M, 1G, etc) - default is 16K
A typical usage scenario is to capture the output of a program in a file. Using curtail prevents the program from creating a runaway file that will eventually fill up the filesystem and cause system failure if not handled at the system level. In the example below, the file my_app_log.txt cannot exceed 2 megabytes in size.
./my_app | curtail -s 2M ./my_app_log.txt
Curtail uses autotools (must be installed on the local system). If not already installed, install the tools using the following commands with the appropriate package manager (apt, yum, etc) for your system:
sudo apt install libtool
sudo apt install automake
sudo apt install autoconf
To build curtail locally, please run the following commands from the base dir of the project:
libtoolize
aclocal
autoheader
autoconf
automake --add-missing
./configure
make
To install in the local system, run the following additional command with appropriate priviledges:
sudo make install
Curtail can also be integrated directly into an application instead of used on the command line. Include the file curtail.h and link the application with -lcurtail. After successfully calling crtl_init, the program's stdout will be directed to the specified file until crtl_term is called.
Curtail is not intended to be a replacement for logrotate. They are fundamentally different. Some of the notable differences are below:
logrotate mitigates runaway files... curtail prevents them.
logrotate requires sysadmin... curtail does not.
logrotate creates multiple files... curtail only one.