You can always use two instances of rsyslog. One for local logs and
another for forwarding logs from remote.
Of course you'll need to create a unit file for systemd to start
rsyslogd with your own config file.
I think that's the easiest approach.
Mariusz Kruk
Ekspert ds. Bezpieczeństwa IT
COMP S.A.
Pion Cyberbezpieczeństwa i Zarządzania Ryzykiem
e-mail: [email protected]
e-mail: [email protected]
tel: +48 608 623 299
On 31.08.2020 10:27, David CAPG via rsyslog wrote:
Hi,
I've found a pcs cluster for rsyslog at work (quite old but it's not the
topic :) ), in active/passive mode (HA)
One resource on the cluster manage the rsyslog service (lsb:rsyslog), and
... the service rsyslog is configured too to run at start.
For me, with PCS if a service is managed by pcs, it must be disable at
system level.
But, if i disable rsyslog at system level, on the slave inactive node, i
got no more logs for local services, like /var/log/secure, messages,....
I try to find a how-to for this case, but hard even for google :) (find
only how to log PCS clustrs, ...)
Thx for any help.
David
_______________________________________________
rsyslog mailing list
https://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.
_______________________________________________
rsyslog mailing list
https://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.