I have a facility (local5) which incorrectly uses alert (should have
been info).
My config file includes
*.emerg /var/log/00_emerg.log
*.alert /var/log/01_alert.log
*.crit /var/log/02_crit.log
*.err -/var/log/03_err.log
*.warn -/var/log/04_warn.log
local5.info -/var/log/local5.info
This causes all my "there's troubles" logs to have these messages.
1) Is my configuration concept just plain wrong?
Should I be using rsyslog extension like
*.=emerg /var/log/00_emerg.log
*.=alert /var/log/01_alert.log
*.=crit /var/log/02_crit.log
*.=err -/var/log/03_err.log
*.=warn -/var/log/04_warn.log
local5.info -/var/log/local5.info
2) what is the best was to have local5.alert messages go to
/var/log/local5.info
Running on PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
rsyslogd 8.1901.0 (aka 2019.01) compiled with:
PLATFORM: arm-unknown-linux-gnueabihf
PLATFORM (lsb_release -d):
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support: Yes
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
memory allocator: system default
Runtime Instrumentation (slow code): No
uuid support: Yes
systemd support: Yes
Number of Bits in RainerScript integers: 64
Thanks for your help.
Any comments/suggestions welcome.
Sinerely,
Dennis German
_______________________________________________
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.
