Query: lcf
OS: linux
Section: 1
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
LCF(1) Debian GNU/Linux manual LCF(1)NAMElcf - Determine which of the historical versions of a config is installedSYNOPSISlcf [options] <Destination File Name> <Historical MD5SUM source directory>DESCRIPTIONThis script, given a destination file name, and a directory containing md5sums of historical versions of the file, attempts to determine if the installed version corresponds to a historical version. lcf uses the same algorithm that ucf uses, and should exhibit the same behav- iour. The source directory is the place where historical md5sums are expected to live. Specifically, the historical md5sums are looked for in either the file ${filename}.md5sum, or the subdirectory ${filename}.md5sum.d/OPTIONS-h, --help Print a short usage message -n, --no-action Dry run. Print the actions that would be taken if the script is invoked, but take no action. -d [n], --debug [n] Set the debug level to the (optional) level n (n defaults to 1). This turns on copious debugging information. -v, --verbose Make the script be very verbose about setting internal variables.FILES/var/lib/ucf/hashfile, /etc/ucf.confSEE ALSOucf(1) ucf.conf(5).BUGSThere are no bugs. Any resemblance thereof is delirium. Really.AUTHORThis manual page was written Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system. Debian Feb 1 2002 LCF(1)
Related Man Pages |
---|
ucf.conf(5) - linux |
ucf.conf(5) - debian |
ucf.conf(5) - netbsd |
ucf.conf(5) - centos |
ucf.conf(5) - v7 |
Similar Topics in the Unix Linux Community |
---|
script to watch changes on a directory |
Can't save a file |
Making a script to copy files not seen before (using md5sum) |
[md5sum] script |