Commit 09797ed1 authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(Invoking dbck): Mention that dbck with no argument will examine the

	database without modifying it.
(General Options): Document -h (aka --help).
(Format Conversion Options): Minor layout fix.
(Notes): Typos fixed.
(Files): Markup fixes.
parent 30b2229e
\input texinfo
@c $Id: dbck.texi,v 1.1 1999/01/13 12:00:17 byers Exp $
@c $Id: dbck.texi,v 1.2 1999/04/03 15:33:42 ceder Exp $
@c %**start of header
@setfilename dbck.info
@settitle "dbck Reference Manual"
......@@ -104,6 +104,9 @@ functions:
The functionality of dbck is controlled through command-line switches.
These are documented below.
If @code{dbck} is invoked without any options it will read the database
and report on its integrity. No files will be modified.
@menu
* General Options:: Controlling the overall behavior of dbck.
* Database Repair Options:: Repairing errors in the LysKOM database.
......@@ -120,6 +123,10 @@ These are documented below.
These options control the general behavior of lyskomd.
@table @asis
@item @code{-h} or @code{--help}
Give a usage message (which includes the version number and the
compiled-in default location of the config file) and exit immediately.
@item @code{-v} or @code{--verbose}
Verbose mode. Report not only errors but the status of the database.
......@@ -171,13 +178,13 @@ to another, you will probably have to give this option.
@item @code{-o} or @code{--output-version}
This option is used to set the output version of the database. This
option will normally be used in conjunction with the @code{-F} option.
@end table
Version 1.9 of @code{lyskomd} requires database version 1; version 2.0
requires database version 2. Versions of @code{lyskomd} prior to 1.9
requires database version 0. Note that information is irrevocably lost
when converting from a higher to a lower database version. This options
requires an argument: the output format version.
@end table
@node Database Maintenance Options, Reporting Options, Format Conversion Options, Invoking dbck
......@@ -250,11 +257,11 @@ Print ``Checking @i{text-no}'' for every text that examined.
@comment node-name, next, previous, up
@chapter Notes
The messages ``Conference @i{conf-no} has a bad Text-list. Starts with
0'' and ``Person @i{pers-no} has created @i{num} conferences, no @i{num}
(as said in person-stat).'' are normal. If tou get them when you specify
the @code{-g} option, let @code{dbck} repair them and run @code{dbck -g}
again.
The messages ``Conference @var{conf-no} has a bad Text-list. Starts with
0'' and ``Person @var{pers-no} has created @var{num} conferences, not
@var{num} (as said in person-stat).'' are normal. If you get them when
you specify the @code{-g} option, let @code{dbck} repair them and run
@code{dbck -g} again.
@node Files, Bugs, Notes, Top
......@@ -266,19 +273,19 @@ dbck uses the same files as @code{lyskomd} (@xref{(lyskomd)}.)
All file names can be changed in the server configuration file.
@xref{(lyskomd)Parameters}.
@table @code
@table @file
@item /usr/lyskom
Default value of @i{prefix}. The default of this value is set at compile
Default value of @code{Prefix}. The default of this value is set at compile
time, but it can be changed in the server configuration file.
@xref{(lyskomd)Parameters}.
@item @i{prefix}/db/lyskomd-data
Half of the database: all status information. This
@item @code{Prefix}/db/lyskomd-data
Half of the database: all status information.
@item @i{prefix}/db/lyskomd-texts
@item @code{Prefix}/db/lyskomd-texts
The other half of the database: the actual texts.
@item @i{prefix}/db/lyskomd-backup
@item @code{Prefix}/db/lyskomd-backup
A backup copy of @code{lyskomd-data}. Never, ever delete this file
unless you know what you are doing, or you may lose the entire data
base. Most of the time this is the only complete database file!
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment