socklog can be run as an ucspi application to listen to an unix domain stream socket and for more flexible distributed logging.
If the environment variables $UID and/or $GID are present, socklog drops permissions to those ids after creating and binding the socket (not in ucspi mode).
socklog converts syslog facility and priority information to names (facility.priority:) as found in /usr/include/syslog.h at compile time if present.
On solaris socklog also accepts sun_stream as first argument. Please see the web page for details.
Starting socklog with the 1st argument unix, socklog will listen to the unix domain socket path. If path is omitted, the default /dev/log is used.
The 1st argument may be omitted, default is unix.
Starting socklog with the 1st argument inet, socklog will listen to the inet udp socket ip:port.
If ip starts with 0, socklog will bind to all local interfaces.
If port is less or equal 1024, socklog must be run by root.
port may be omitted, default is 514. ip may be omitted, default is 0.
socklog prepends a.b.c.d: to each syslog message it receives, where a.b.c.d is the ip address of the connecting system.
Starting socklog with the 1st argument ucspi, socklog will run as an ucspi application. Normally socklog will only be started in ucspi mode by an ucspi server tool, such as tcpsvd(8), tcpserver(1) or unixserver.
For each arg, socklog will prepend $arg: to each syslog message, if the environment variable $arg is present (maximum is 8).
Table of Contents