A very short section which just doesn't seem to belong anywhere else.
Epos supports error logging via syslog (on systems where syslogd
is running). At the moment, only (the most of) TTSCP completion codes
together with the associated messages can be logged; this includes
all abnormal server termination states (except for a plain old fatal
signal). If syslog should be available (the
file is present), but isn't, the error messages are logged directly
to the system console. If the syslog facility is being missed at
compilation time, Epos opens a file called
epos.err in the
current directory whatever it may be and writes some debugging
information there instead.
The syslog message levels are set according to the
syslog message levels table. In all cases, Epos messages
are logged with the
||trivial success TTSCP codes|
||silly errors and other messages|
||shutting down as requested|
||security or network error|
See also the <tt>authpriv</tt> option which may change this behavior for possibly security-related errors, but not network errors.
Any debugging output together with error messages etc. is also often logged
/var/log/epos as specified with the
The agent profile which shows how much time does Epos spend with individual agents (which gives an insight into which processing phases are time consuming) can be turned on with the <tt>profile</tt> option.