I am seeing red messages even though it is a successful start because tac_plus is sending message to a wrong log level or it does not have proper systemd implementation?
*●* tacacs@cc.service - TACACS+ daemon instance tacacs-cc Loaded: loaded (/etc/systemd/system/tacacs@.service; enabled; vendor preset: disabled) Active: *active (running)* since Fri 2018-02-09 04:02:22 UTC; 13h ago Docs: man:tac_plus(8) man:tac_plus.conf(5) Process: 15379 ExecReload=/bin/sh -c /home/audit/bin/tacsanity /etc/tacacs/tacacs-%i.conf && /bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 18131 (tac_plus) CGroup: /system.slice/system-tacacs.slice/tacacs@cc.service └─18131 /usr/local/sbin/tac_plus -G -L -B 100.75.8.233 -C /etc/tacacs/tacacs-cc.conf -l /var/log/tacacs/tacacs-cc.daemon.log -p 49 -d 8 -d 16 Feb 09 17:32:21 tacacs.example.net systemd[1]: Reloaded TACACS+ daemon instance tacacs-cc. Feb 09 17:32:21 tacacs.example.net tac_plus[18131]: Received signal Feb 09 17:32:21 tacacs.example.net tac_plus[18131]: Version F4.0.4.28 Initialized 3 Feb 09 17:32:49 tacacs.example.net tac_plus[15392]: *Attempting to lock /tmp/tmp.9YI9LTwhGc.log fd 3* Feb 09 17:32:49 tacacs.example.net tac_plus[15392]: *Successfully locked /tmp/tmp.9YI9LTwhGc.log fd 3 after 1 tries* Feb 09 17:32:49 tacacs.example.net tac_plus[15392]: Reading config Feb 09 17:32:50 tacacs.example.net systemd[1]: Reloaded TACACS+ daemon instance tacacs-cc. Feb 09 17:32:50 tacacs.example.net tac_plus[18131]: Received signal Feb 09 17:32:50 tacacs.example.net tac_plus[18131]: Reading config Feb 09 17:32:50 tacacs.example.net tac_plus[18131]: Version F4.0.4.28 Initialized 4 Also journalctl -o export _SYSTEMD_UNIT=tacacs@cc.service -e does show only those two lines are using syslog priority 3 (error) and hence the red. Trying to see what's the reason behind picking priority 3 (error) for these two lines, instead of priority 5 (notice) or priority 6 (info) like rest of the messages in there? Attempting to lock .... Successfully locked ... Thanks -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.shrubbery.net/pipermail/tac_plus/attachments/20180209/893ebfe2/attachment.html> _______________________________________________ tac_plus mailing list tac_plus@shrubbery.net http://www.shrubbery.net/mailman/listinfo/tac_plus