lights(1p) [debian man page]
LIGHTS(1p) User Contributed Perl Documentation LIGHTS(1p) NAME
lights - DNSSEC-Tools Rollover Overview GUI Display SYNOPSIS
lights [options] DESCRIPTION
lights gives a very simple overview of the rollover status of a set of zones. The rollover status counts are given in a "traffic light" display. In contrast, blinkenlights gives a detailed display of the roll status of a set of zones. lights gives very little control over rollerd, the way blinkenlights does. lights can halt rollerd's execution only. The rollover status is retrieved in one of two ways. By default, rollerd is contacted via the rollctl command. Alternately, if the -rrf option is given, then zone status is read directly from a rollrec file. The default method gets the status directly from rollerd and the user need not know the location of the relevant rollrec file. However, that method will not get zone status until rollerd is available to respond to the information request. Consequently, the alternate method allows lights to bypass communicating with rollerd and not having to wait for rollerd to be available. A window is created that has three colored sections - green, yellow, and red. The green section displays a count of those zones that are in "normal" status; that is, they are not in rollover. The yellow section displays a count of those zones that are in rollover. The red section displays a count of those zones that are in need of attention. A common cause for this last state is because a zone is in phase 6 of KSK rollover and is waiting for its parent zone to publish the child's new DS record. Clicking on the color rows in the main window will bring up a dialog box that lists the zones in that state. This list will not automatically update as zones change rollover state. OPTIONS
lights supports the following options. -interval wait-time Interval between checks of zone rollover status By default, wait-time is given in minutes. This can be adjusted by specifying one of the following time-unit suffixes. * s - seconds * m - minutes * h - hours Examples: * -interval 24 - 24 minutes * -interval 24s - 24 seconds * -interval 24m - 24 minutes * -interval 24h - 24 hours -rrf rollrec-file A rollrec file to be read for zone status. -labels Labels will be given for each color field in the GUI. -verbose Give verbose output. -help Give a usage message and exit. -Version Displays the version information for lights and the DNSSEC-Tools package. REQUIREMENTS
lights is implemented in Perl/Tk, so both Perl and Perl/Tk must be installed on your system. KNOWN ISSUES
The following are known issues. These will be resolved in the fullness of time. o Resizing the window leaves the color blobs in their original size. This is an issue with the Tk widget used to display the color stripes. Other display methods are being investigated... COPYRIGHT
Copyright 2010-2012 SPARTA, Inc. All rights reserved. See the COPYING file included with the DNSSEC-Tools package for details. AUTHOR
Wayne Morrison, tewok@tislabs.com SEE ALSO
blinkenlights(8), bubbles(8), rollerd(8), rollrec(5) perl v5.14.2 2012-06-21 LIGHTS(1p)
Check Out this Related Man Page
ROLLCHK(1p) User Contributed Perl Documentation ROLLCHK(1p) NAME
rollchk - Check a DNSSEC-Tools rollrec file for problems and inconsistencies. SYNOPSIS
rollchk [-roll | -skip] [-count] [-quiet] [-verbose] [-help] rollrec-file DESCRIPTION
This script checks the rollrec file specified by rollrec-file for problems and inconsistencies. TYPES OF CHECKS
There are three types of checks performed by rollchk: file checks, "raw" file checks, and rollrec checks. The checks are performed in that order, and if any of the group checks fail then rollchk exits. File Checks These checks determine basic information about the rollrec file itself. Recognized problems are: o non-existent rollrec file The specified rollrec file does not exist. o non-regular rollrec file The specified rollrec file is not a regular file. Raw File Checks These checks are performed directly on the file contents, rather than by using the rollrec.pm interfaces. Recognized problems are: o duplicated rollrec names A rollrec name is not unique. Rollrec Checks These checks are performed after referencing the file contents with the the rollrec.pm interfaces. Recognized problems are: o no zones defined No zones are defined in the specified rollrec file. o invalid KSK rollover phase A zone has an invalid KSK rollover phase. These phases may be 0, 1, 2, 3, 4, 5, 6, or 7; any other value is invalid. o mismatch in KSK timestamp data A zone's KSK roll-seconds timestamp does not translate into the date stored in its roll-date string. o invalid ZSK rollover phase A zone has an invalid ZSK rollover phase. These phases may be 0, 1, 2, 3, or 4; any other value is invalid. o mismatch in ZSK timestamp data A zone's ZSK roll-seconds timestamp does not translate into the date stored in its roll-date string. o contemporaneous KSK and ZSK rollovers A zone has a KSK rollover occurring at the same time as a ZSK rollover. A zone may only have one rollover phase be non-zero at a time. o in rollover without a phasestart A zone is currently in rollover, but its rollrec record does not have a phasestart field. o empty administrator A zone has an empty administrator field. This field must contain a non-empty data value. The value itself is not parsed for accuracy. o non-existent directory Several checks are made for a zone's directory. If the zone has a directory specified, the directory must exist and it must be an actual directory. o invalid display flag A zone has an invalid display flag. This flag may be 0 or 1; any other value is invalid. o non-positive maxttl The maximum TTL value must be greater than zero. o zone file checks Several checks are made for a zone's zone file. The zone file must exist, it must be a regular file, and it must not be of zero length. If the file is not an absolute path and the file's rollrec has a directory entry, then the directory is prepended to the filename prior to performing any checks. o keyrec file checks Several checks are made for a zone's keyrec file. The keyrec file must exist, it must be a regular file, and it must not be of zero length. If the file is not an absolute path and the file's rollrec has a directory entry, then the directory is prepended to the filename prior to performing any checks. o zonename checks Several checks are made for zonename. The zonename must maatch the SOA name in the zone file, and the zonename's keyrec record in its keyrec file must be a zone record. o empty zsargs A zone has an empty zonesigner-arguments field. If this field exists, it must contain a non-empty data value. The value itself is not parsed for accuracy. OPTIONS
-roll Only display rollrecs that are active ("roll") records. This option is mutually exclusive of the -skip option. -skip Only display rollrecs that are inactive ("skip") records. This option is mutually exclusive of the -roll option. -count Display a final count of errors. -quiet Do not display messages. This option supersedes the setting of the -verbose option. -verbose Display many messages. This option is subordinate to the -quiet option. -Version Displays the version information for rollchk and the DNSSEC-Tools package. -help Display a usage message. COPYRIGHT
Copyright 2006-2012 SPARTA, Inc. All rights reserved. See the COPYING file included with the DNSSEC-Tools package for details. AUTHOR
Wayne Morrison, tewok@tislabs.com SEE ALSO
lsroll(8), rollerd(8), rollinit(8) Net::DNS::SEC::Tools::rollrec.pm(3) file-rollrec(5), keyrec(8) perl v5.14.2 2012-06-21 ROLLCHK(1p)