On Tue, 3 Feb 2015, Michael Biebl wrote:
2015-02-03 20:52 GMT+01:00 Michael Biebl <[email protected]>:
Oh, no, you don't need this.
If rsyslog is activated by systemd, it will pass this socket as
socket-activated, to be precise.
environment variable to rsyslog and rsyslog will pick that up
automatically.
There is nothing you need to do.
If you look at a distro like Debian, which runs rsyslog under systemd,
you'll see that it simply ships a generic /etc/rsyslog.conf.
You just need to make sure to install and enable the rsyslog.service
file that is provided by rsyslog.
The magic bits are:
[Unit]
Requires=syslog.socket
...
[Alias]
Alias=syslog.service
This will make systemd start rsyslog if there is activity on /dev/log
and start rsyslog.service, passing it the syslog socket in the
LISTEN_FDS env variable, where rsyslog will pick it up automatically.
I'm happy to go into more detail, if there is interest.
It would be useful. Questions relating to interacting with the journal and
systemd are common and going to be more common, but there aren't a lot of us
here with experience with that environment.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
