logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

lcf - Determine which of the historical versions of a config is installed

Author

       This manual page was written Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system.

Debian                                             Feb 1 2002                                             LCF(1)

Bugs

       There are no bugs.  Any resemblance thereof is delirium. Really.

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/

Files

/var/lib/ucf/hashfile,/etc/ucf.conf

Name

       lcf - Determine which of the historical versions of a config is installed

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.

See Also

ucf(1) ucf.conf(5).

Synopsis

lcf[options]<DestinationFileName><HistoricalMD5SUMsourcedirectory>

See Also