Re: systemd & postgresql - flooding system log
On Sun, 16 Jul 2017, Václav Ovsík wrote:
> On Sun, Jul 16, 2017 at 12:01:56PM +0200, Václav Ovsík wrote:
> > OMG, I don't looked into /var/log/auth.log :(
> >
> > Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
> > Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session opened for user postgres by (uid=0)
> > Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
> > Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session opened for user postgres by (uid=0)
> > Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
> >
> > No, I'm going back to LogLevel notice setting of systemd. :(
This is not systemd logging this, but pam_unix.so.
> With su is /var/log/auth.log flooded too, I didn't noticed before :-/
> (logcheck was filtering this).
If you don't care about this in your log, then you can either filter it,
or comment out pam_unix in /etc/pam.d/common-session-noninteractive.
--
Don Armstrong https://www.donarmstrong.com
Religion is religion, however you wrap it, and like Quell says, a
preoccupation with the next world clearly signals an inability to cope
credibly with this one.
-- Richard K. Morgan "Broken Angels" p65
Reply to: