[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
You will no doubt want to log your GGZ server's activity. Setting up logging, and the details to log, to a file is almost completely self-explanatory in the ggzd.conf file. Setting up logging via the syslog facility may be less than obvious.
Logging via syslogd is the default unless you specify a log file (either in ggzd.conf or on the command line). By default, log entries from the GGZ server will go to the facility local0. This can be specified in ggzd.conf.
You will however, need to setup your /etc/syslog.conf file to log those messages from facility local0 (or whatever you choose) into a specific file, probably /var/log/ggzd.
If you compiled the GGZ server with debugging enabled, it will generate extra information which you may want to go to a separate file. If you are are not using syslog then this is configurable in ggzd.conf. If you *are* using syslog, here is a convenient set of syslog.conf entries to separate debug messages from standard log messages:
local0.info /var/log/ggzd.log local0.=debug /var/log/ggzd.debug
Put those two lines into your syslog.conf, restart syslogd and your log nightmares are over.
To test a server's communication with a single client, the DumpFile variable can be filled with either a file name or a virtual file name such as stderr.