From 071c9b511a711725537eff386f82a3af3ca930a8 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Date: Fri, 4 Sep 2009 14:53:44 +0200
Subject: added $LogRSyslogStatusMessages configuration directive
...permitting to turn off rsyslog start/stop/HUP messages. See Debian
ticket http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463793
---
doc/manual.html | 2 +-
doc/rsyslog_conf_global.html | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
(limited to 'doc')
diff --git a/doc/manual.html b/doc/manual.html
index e1f7480e..52a8380e 100644
--- a/doc/manual.html
+++ b/doc/manual.html
@@ -19,7 +19,7 @@ rsyslog support available directly from the source!
Please visit the rsyslog sponsor's page
to honor the project sponsors or become one yourself! We are very grateful for any help towards the
project goals.
-This documentation is for version 4.5.2 (v4-beta branch) of rsyslog.
+
This documentation is for version 4.7.0 (v4-devel branch) of rsyslog.
Visit the rsyslog status page
to obtain current version information and project status.
If you like rsyslog, you might
diff --git a/doc/rsyslog_conf_global.html b/doc/rsyslog_conf_global.html
index 2bbb136e..f2642ca4 100644
--- a/doc/rsyslog_conf_global.html
+++ b/doc/rsyslog_conf_global.html
@@ -146,6 +146,10 @@ Usually that should not be a big issue, as the restart-type HUP can easily be re
something along the lines of "/etc/init.d/rsyslog restart".
$IncludeConfigMainMsgQueueCheckpointInterval <number>
+$LogRSyslogStatusMessages [on/off] - If set to on (the default),
+rsyslog emits message on startup and shutdown as well as when it is HUPed.
+This information might be needed by some log analyzers. If set to off, no such
+status messages are logged, what may be useful for other scenarios.
$MainMsgQueueDequeueSlowdown <number> [number
is timeout in microseconds (1000000us is 1sec!),
default 0 (no delay). Simple rate-limiting!]
--
cgit
From 5f76568d3707cbbadfa3767558ded52cf5f27f47 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Date: Fri, 4 Sep 2009 16:58:00 +0200
Subject: added new config option $InputUnixListenSocketCreatePath
backport from v5-devel
---
doc/imuxsock.html | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
(limited to 'doc')
diff --git a/doc/imuxsock.html b/doc/imuxsock.html
index 472470a0..15c365a6 100644
--- a/doc/imuxsock.html
+++ b/doc/imuxsock.html
@@ -46,6 +46,18 @@ Ignore timestamps included in the messages, applies to messages received via the
$SystemLogSocketName <name-of-socket> -- former -p option
$SystemLogFlowControl [on/off] - specifies if flow control should be applied
to the system log socket.
+$InputUnixListenSocketCreatePath [on/off] - create directories in the socket path
+if they do not already exist. They are created with 0755 permissions with the owner being the process under
+which rsyslogd runs. The default is not to create directories. Keep in mind, though, that rsyslogd always
+creates the socket itself if it does not exist (just not the directories by default).
+
Note that this statement affects the
+next $AddUnixListenSocket directive that follows in sequence in the configuration file. It never works
+on the system log socket (where it is deemed unnecessary). Also note that it is automatically
+being reset to "off" after the $AddUnixListenSocket directive, so if you would have it active
+for two additional listen sockets, you need to specify it in front of each one. This option is primarily considered
+useful for defining additional sockets that reside on non-permanent file systems. As rsyslogd probably starts
+up before the daemons that create these sockets, it is a vehicle to enable rsyslogd to listen to those
+sockets even though their directories do not yet exist. [available since 4.7.0 and 5.3.0]
$AddUnixListenSocket <name-of-socket> adds additional unix socket, default none -- former -a option
$InputUnixListenSocketHostName <hostname> permits to override the hostname that
shall be used inside messages taken from the next $AddUnixListenSocket socket. Note that
@@ -57,20 +69,32 @@ that the local hostname can be overridden in cases where that is desired.
This documentation is sparse and incomplete.
Sample:
-The following sample is the minimum setup required to accept syslog messages from applications running on the local system.
+
The following sample is the minimum setup required to accept syslog messages from applications running
+on the local system.
The following sample is a configuration where rsyslogd pulls logs from two
jails, and assigns different hostnames to each of the jails:
-