mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-18 14:30:41 +01:00
7a671da74f
now that rsyslog is usually only installed for real syslog servers, we should assume that some network listening or forwarding happens on start. As such we need to start a bit later, after the network. This poses no problem as systemd nowadays comes with journal which is in almost all cases configured to buffer log data while rsyslog is not yet running. see also https://github.com/rsyslog/rsyslog-pkg-rhel-centos/issues/72
22 lines
522 B
SYSTEMD
22 lines
522 B
SYSTEMD
[Unit]
|
|
Description=System Logging Service
|
|
;Requires=syslog.socket
|
|
Wants=network.target network-online.target
|
|
After=network.target network-online.target
|
|
Documentation=man:rsyslogd(8)
|
|
Documentation=http://www.rsyslog.com/doc/
|
|
|
|
[Service]
|
|
Type=notify
|
|
ExecStart=@sbindir@/rsyslogd -n -iNONE
|
|
StandardOutput=null
|
|
Restart=on-failure
|
|
|
|
# Increase the default a bit in order to allow many simultaneous
|
|
# files to be monitored, we might need a lot of fds.
|
|
LimitNOFILE=16384
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|
|
;Alias=syslog.service
|