Scribd Logo
Upload

Welcome to Scribd!

  • LCF

    Uploaded by

    Soporte Glpi
    2 views1 page
    This script determines which historical version of a configuration file is installed by comparing the file's MD5 checksum to checksums stored in a historical directory. It has options to run in dry-run, verbose, or debug modes. It uses the same algorithm as the ucf script and should behave the same way.

    Original Description:

    Programa que permite revisar configuraciones de lc en linux.

    Original Title

    lcf

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This script determines which historical version of a configuration file is installed by comparing the file's MD5 checksum to checksums stored in a historical directory. It has options to run in dry-run, verbose, or debug modes. It uses the same algorithm as the ucf script and should behave the same way.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    2 views1 page

    LCF

    Uploaded by

    Soporte Glpi
    This script determines which historical version of a configuration file is installed by comparing the file's MD5 checksum to checksums stored in a historical directory. It has options to run in dry-run, verbose, or debug modes. It uses the same algorithm as the ucf script and should behave the same way.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    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 histor‐
    ical 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 subdi‐
    rectory ${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)

    You might also like