lcf
Determine which of the historical versions of a config is installed
see also :
ucf
Synopsis
lcf
[options] <Destination File Name> <Historical
MD5SUM source directory>
add an example, a script, a trick and tips
examples
no example yet ...
... Feel free to add your own example above to help other Linux-lovers !
description
This 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 behaviour.
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.conf
bugs
There are no
bugs. Any resemblance thereof is delirium. Really.
see also
ucf
ucf.conf.
author
This manual
page was written Manoj Srivastava
<srivasta[:at:]debian[:dot:]org>, for the Debian GNU/Linux
system.