| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
to permit the auto-creation of pathes to additional log sockets. This
turns out to be useful if they reside on temporary file systems and
rsyslogd starts up before the daemons that create these sockets
(rsyslogd always creates the socket itself if it does not exist).
|
| |
|
|
| |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | |
|
| |
|
|
|
|
| |
It permits to override the hostname being used on a local unix socket.
This is useful for differentiating "hosts" running in several jails.
Feature was suggested by David Darville, thanks for the suggestion.
|
|
|
made this mode the default; this was needed, as some programs (e.g.
sshd) log with inconsistent timezone information, what messes up the
local logs (which by default don't even contain time zone information).
This seems to be consistent with what sysklogd did for the past four
years. Alternate behaviour may be desirable if gateway-like processes
send messages via the local log slot - in this case, it can be enabled
via the $InputUnixListenSocketIgnoreMsgTimestamp and
$SystemLogSocketIgnoreMsgTimestamp config directives
|
