It is possible to run two instances of syslogd. One instance must
be started so that it processes messages from only the local host
(-i option); the other instance must be
started so that it processes messages from only the network (-n option).
If you run two instances of syslogd, one for local messages and
another for network messages, and you also configure the automatic
archival function, do not configure the same UNIX file destinations in the two configuration
files. The archival function renames, closes, and reopens the UNIX files. If two instances of
syslogd are performing the archival function on the same set of files,
results of the archival function are unpredictable. The same is true
for the configured archive destination data sets. Be sure to configure
unique UNIX file destinations
and archive data set names for the two syslogd instances.
syslogd can run swappable or nonswappable. When an application
makes an address space nonswappable, it might convert additional real
storage in the system to preferred storage. Because preferred storage
cannot be configured offline, allowing syslogd to run in a nonswappable
state can reduce the installation's ability to reconfigure storage
in the future. Use the following guidelines to set the wanted state:
If the FACILITY class resource BPX.STOR.SWAP is not defined to
the system:
syslogd will run nonswappable.
syslogd cannot be prevented from running nonswappable.
If the FACILITY class resource BPX.STOR.SWAP is defined to the
system with UACC(NONE):
syslogd will run swappable by default (no access to BPX.STOR.SWAP).
syslogd can run nonswappable (given at least READ access to BPX.STOR.SWAP).
To define the FACILITY class resource BPX.STOR.SWAP issue the
following commands:
If you want syslogd to receive log data from remote syslogd servers,
ensure that syslogd can bind to UDP port 514 by reserving that port
for the syslogd job in your PROFILE.TCPIP data set. Ensure that the
syslog service is defined in your services file or data set (for example,
/etc/services). The following
example port reservation in PROFILE.TCPIP assumes that syslogd runs
as job syslogd1:
PORT
...
514 UDP syslogd1 ;syslogd daemon
...
The following example shows the services file or
data set file entry:
syslog 514/udp
Configuration file errors are written to the operator console
because initialization is not complete until the entire configuration
file has been read.
Facility mark is not affected by the *.priority usage. Mark messages
are written only to the destinations of rules that specify mark.info.
If a mark interval of zero minutes is specified, mark messages
will be written every thirty seconds.