LCF(1) Debian GNU/Linux manual LCF(1)NAME
lcf - Determine which of the historical versions of a config is installed
SYNOPSIS
lcf [options] <Destination File Name> <Historical MD5SUM source directory>
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 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.conf
SEE ALSO ucf(1)ucf.conf(5).
BUGS
There are no bugs. Any resemblance thereof is delirium. Really.
AUTHOR
This manual page was written Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system.
Debian Feb 1 2002 LCF(1)
Check Out this Related Man Page
LCF(1) Debian GNU/Linux manual LCF(1)NAME
lcf - Determine which of the historical versions of a config is installed
SYNOPSIS
lcf [options] <Destination File Name> <Historical MD5SUM source directory>
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 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.conf
SEE ALSO ucf(1)ucf.conf(5).
BUGS
There are no bugs. Any resemblance thereof is delirium. Really.
AUTHOR
This manual page was written Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system.
Debian Feb 1 2002 LCF(1)
Hi, everybody
I want to know hot to watch changes on a dir, for example if someone changes a file inside it, with an script. I've tried using md5sum and then diff, sadly with no success.
I use md5sum for single files, but doesn't work for directories. The idea is take a snapshot with md5sum,... (4 Replies)
There is a file A.lcf.
I am updating the file and saving it .
But as soon as I am logging off and then logging in I am finding that the updated changes are not there in the file. (5 Replies)
Hello,
I would like to make a script that searches through a SRC folder and copies only files it's never seen before to a DEST folder.
SRC = /user/.phonesync/photos-backup
DST = /usr/.phonesync/photos-new
So basically, I'd start with a:
md5sum /user/.phonesync/photos-backup/* >... (29 Replies)
I am getting No such file or directory if my variable contains white spaces... Is there a way to fix this?
This works
x="1.md5"
md5sum -c "$x"
This, does not
x="23\ 5\ 6\ 7\ 8\ 9\ 10.md5"
md5sum -c "$x"
md5sum: '23\ 5\ 6\ 7\ 8\ 9\ 10.md5': No such file or directory
How do I fix... (1 Reply)