From ffb1f41441d28ec6af3ac3ad64500718f1ae4b57 Mon Sep 17 00:00:00 2001 From: Michael Hampton Date: Mon, 15 Mar 2004 16:48:22 +0000 Subject: [PATCH] * Documentation update: update citadel.html for new syslog logging --- citadel/ChangeLog | 4 ++++ citadel/docs/citadel.html | 25 ++++++++++++++----------- citadel/techdoc/developers.txt | 1 + 3 files changed, 19 insertions(+), 11 deletions(-) diff --git a/citadel/ChangeLog b/citadel/ChangeLog index 4c90500e8..ff2a48b1a 100644 --- a/citadel/ChangeLog +++ b/citadel/ChangeLog @@ -1,4 +1,7 @@ $Log$ + Revision 614.80 2004/03/15 16:48:22 error + * Documentation update: update citadel.html for new syslog logging + Revision 614.79 2004/03/15 16:47:04 error * msgbase.c: cmd_move(): Fix the security logic for non-aides trying to move or copy messages. The logic should do the following: @@ -5524,3 +5527,4 @@ Sat Jul 11 00:20:48 EDT 1998 Nathan Bryant Fri Jul 10 1998 Art Cancro * Initial CVS import + diff --git a/citadel/docs/citadel.html b/citadel/docs/citadel.html index 2d0dba4f7..4bbcaee2d 100644 --- a/citadel/docs/citadel.html +++ b/citadel/docs/citadel.html @@ -844,16 +844,19 @@ program against to set up some data files. If a directory is not specified, the directory name which was specified in the Makefile will be used.

-xDebugLevel - Set the verbosity of trace messages printed. -The -available debugging levels are:

+When -x is used, it will suppress messages sent to syslog (see below). In +other words, syslog will never see certain messages if -x is used. Normally +you should configure logging through syslog, but -x may still be useful in +some circumstances. The available debugging levels are:

    -
  • 1 - Internal errors (failed thread creation, malloc problems, -etc.)
    • -
  • 2 - Network errors (broken sockets, failed socket creation)
    • -
  • 3 - Begin and end of sessions, startup/shutdown of server
    • -
  • 5 - Server commands being sent from clients
    • -
  • 7 - Entry and exit of various functions
    • -
  • 9 - Various debugging checkpoints (insanely verbose)
    • +
  • 0 - Emergency condition; Citadel will exit immediately
    • +
  • 1 - Severe errors; Citadel may be unable to continue without attention
    • +
  • 2 - Critical errors; Citadel will continue with degraded functionality
    • +
  • 3 - Error conditions; Citadel will recover and continue normally
    • +
  • 4 - Warning messages; Citadel will continue normally
    • +
  • 5 - Normal operational messages
    • +
  • 6 - Informational messages, progress reports, etc.
    • +
  • 7 - Debugging messages; extremely verbose

-tTraceFile - Tell the server where to send its debug/trace output. Normally it is sent to stdout.

@@ -877,8 +880,8 @@ entry in your /etc/inittab file. This will conveniently bring the server up when your system is up, and terminate it gracefully when your system is shutting down. The exact syntax for your system may vary, but here's an entry that could be used on a Linux system:

-
cit:2345:respawn:/usr/local/citadel/citserver -h/usr/local/citadel -t/dev/tty9 -x3
-

In this example, we've chosen debugging level 3, and have the trace +

cit:2345:respawn:/usr/local/citadel/citserver -h/usr/local/citadel -t/dev/tty9 -x6
+

In this example, we've chosen debugging level 6, and have the trace stuff output to one of the virtual consoles. It's important to remember to turn off any getty that is set up on that virtual console, if you do this. After making this change, the command init q works on diff --git a/citadel/techdoc/developers.txt b/citadel/techdoc/developers.txt index 78df37d5d..a88b7d879 100644 --- a/citadel/techdoc/developers.txt +++ b/citadel/techdoc/developers.txt @@ -46,6 +46,7 @@ Developer codes (and where known, client codes) Client Name Status Description 0 libcitadel in development Client-side API library 1 D.O.C. dead Dave's Own Citadel look-alike + 8 stress in development Citadel server stress tester 16 Courier in development GTK+ Unix/Win32 Client 69 Anticlimactic Teleservices -- 2.39.2