https://bugzilla.novell.com/show_bug.cgi?id=728565
https://bugzilla.novell.com/show_bug.cgi?id=728565#c40
--- Comment #40 from Marius Tomaschewski 2012-02-10 13:28:40 UTC ---
I'd like to propose an another approach:
We define a new sysconfig variable allowing the user to override
the detection:
## Type: list("",yes,no)
## Default: ""
SYSLOG_REQUIRES_NETWORK=""
Using this variable, we can drop the autodetection code for rsyslogd
completely and act as defined in the variable.
When the variable isn't set to "yes", rsyslog will be started early,
but without to use the early config -- it is smart enough to handle
most cases when the correct config lines has been commented out in
the /etc/rsyslog.d/remote.conf:
# An on-disk queue is created for this action. If the remote host is
# down, messages are spooled to disk and sent when it is up again.
$WorkDirectory /var/spool/rsyslog # where to place spool files
$ActionQueueFileName uniqName # unique name prefix for spool files
$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible)
$ActionQueueSaveOnShutdown on # save messages to disk on shutdown
$ActionQueueType LinkedList # run asynchronously
$ActionResumeRetryCount -1 # infinite retries if host is down
# Remote logging via UDP
# remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional
*.* @172.16.20.200
it also works when rsyslog listens:
# UDP Syslog Server:
$ModLoad imudp.so # provides UDP syslog reception
#$UDPServerAddress 172.16.20.1
$UDPServerRun 514 # start a UDP syslog server at standard port 514
_except_ the user is trying to bind a specific IP address using the
$UDPServerAddress 172.16.20.1
line [as the IP not set when network is stopped or not yet started].
The on-disk queue are required settings also in case of the another
possibilities, such as logging into sql database, ...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.