Re: [DNG] disable elogind messages?
On 11/24/19 10:48 AM, Andreas Messer wrote: On Sun, Nov 24, 2019 at 07:14:48AM -0600, hal wrote: [...] I've commented out all of these lines. Presumably elogind-user is absolutely pointless on a Devuan system anyway? a) either run "/usr/sbin/pam-auth-update" and unmark elogind entry in the dialog appearing (This will actually change all /etc/pam.d/common* files permanently). And disable elogind service running "/usr/sbin/update-rc.d elogind remove" Thanks! Much better than hand editing. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On Sun, Nov 24, 2019 at 07:14:48AM -0600, hal wrote: > > [...] > I've commented out all of these lines. Presumably elogind-user is > absolutely pointless on a Devuan system anyway? Hmm, I wouldn't edit /etc/pam.d/common-* directly. Contents in these files are managed and may/might change during package upgrade/install back. Also on a desktop machine I would choose elogind to be working for normal logins since it is needed for most desktop environments to mount/unmount removable media and to shutdown/reboot the system. If you really want do disable elogind for everything I would recommend to: a) either run "/usr/sbin/pam-auth-update" and unmark elogind entry in the dialog appearing (This will actually change all /etc/pam.d/common* files permanently). And disable elogind service running "/usr/sbin/update-rc.d elogind remove" b) Or just remove libpam-elogind and probably also elogind itself (if its not a dependency of some other package) Otherwise I'd suggest to only edit /etc/pam.d/ files to disable elogind for corresponding service if needed. This should only be required for files including "common-session". cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On 11/24/19 4:57 AM, Andreas Messer wrote: Sorry, did not read your E-Mail before. Did you check /etc/pam.d/cron for elogind references? (Including the includes) cron should not produce any elogind output since it uses /etc/pam.d/common-session-noninteractive by default. elogind should be only listed in /etc/pam.d/common-session. No problem. Thank you for taking the time for this. So grep shows this: # grep elogind /etc/pam.d/* /etc/pam.d/common-session:session optional pam_elogind.so /etc/pam.d/elogind-user:session optional pam_elogind.so And contents of elogind-user are: # This file is part of systemd. # # Used by systemd --user instances. account required pam_unix.so session required pam_selinux.so close session required pam_selinux.so nottys open session required pam_loginuid.so session optional pam_keyinit.so force revoke session optional pam_elogind.so I've commented out all of these lines. Presumably elogind-user is absolutely pointless on a Devuan system anyway? Thanks again ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On Sat, Nov 23, 2019 at 05:38:54AM -0600, hal wrote: > This still leaves the question however, is there a way to disable the > elogind messages in syslog? It seems like a lot of useless chatter in the > syslogs. Sorry, did not read your E-Mail before. Did you check /etc/pam.d/cron for elogind references? (Including the includes) cron should not produce any elogind output since it uses /etc/pam.d/common-session-noninteractive by default. elogind should be only listed in /etc/pam.d/common-session. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On 11/23/19 2:17 AM, Erik Christiansen wrote: But there's no earthly need for cron, if you run fetchmail as a daemon. Mine polls the hosts nominated in ~/.fetchmailrc each 600 seconds, delivering to port 25. Postfix then invokes procmail for message delivery sorting. (Probably don't need postfix, but it's a habit of over 30 years to have an MTA.) Well, years ago (more than 10?) I did run fetchmail as a daemon but it would sometimes hang or just die leaving my dovecot inbox silent for days before I would know something was wrong. I couldn't figure out where the issue was so cron was the work-around. You make a good point however and get me thinking... I should change my setup to fetchmail as a daemon again (a lot changes with software overa a couple years) and perhaps monitor the status with SMS. This still leaves the question however, is there a way to disable the elogind messages in syslog? It seems like a lot of useless chatter in the syslogs. Thanks ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On Sat, 23 Nov 2019 19:17:07 +1100, Erik wrote in message <20191123081707.GA3481@ratatosk>: > On 19.11.19 05:12, hal wrote: > > My mail server is doing the exact same thing when running fetchmail > > for several accounts. Every few minutes cron rolls through 4 or 5 > > accounts, runs fetchmail, and terminates leaving all those > > `elogind` messages in syslog. > > But there's no earthly need for cron, if you run fetchmail as a > daemon. Mine polls the hosts nominated in ~/.fetchmailrc each 600 > seconds, delivering to port 25. Postfix then invokes procmail for > message delivery sorting. (Probably don't need postfix, but it's a > habit of over 30 years to have an MTA.) ..simply use "mda '/usr/bin/procmail' " as the last line in your .fetchmailrc. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On 19.11.19 05:12, hal wrote: > My mail server is doing the exact same thing when running fetchmail for > several accounts. Every few minutes cron rolls through 4 or 5 accounts, > runs fetchmail, and terminates leaving all those `elogind` messages in > syslog. But there's no earthly need for cron, if you run fetchmail as a daemon. Mine polls the hosts nominated in ~/.fetchmailrc each 600 seconds, delivering to port 25. Postfix then invokes procmail for message delivery sorting. (Probably don't need postfix, but it's a habit of over 30 years to have an MTA.) Erik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
On 11/13/19 4:43 AM, Mark Hindley wrote: [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64972. [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64973 of user root. [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64973. That is 6 new root sessions in 2 seconds. What is in your cron job? I can't immediately think of a reason why you would want a logind session for a root cron job at all. I think this might be from a cronjob running the sar command to collect system info to graph (CPU, free ram, cpu temp, etc). Some of the data gathering is only seconds long, however it spawns a new instance of `sar -u` or `sar -B`, etc. My mail server is doing the exact same thing when running fetchmail for several accounts. Every few minutes cron rolls through 4 or 5 accounts, runs fetchmail, and terminates leaving all those `elogind` messages in syslog. It may be since I'm using bash in the scripts called by cron, this is creating a login shell. Could that be what's causing all this noise? Thanks and apologies for the belated reply ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] disable elogind messages?
Hal, On Wed, Nov 13, 2019 at 04:35:14AM -0600, hal wrote: > Hi, > Any way to disable elogind from filling up the message logs? I think all > these messages are happening because I have cron jobs running frequently. > > I could possibly tell rsyslog to file these in cron.log (if it is cron) but > there is still the problem of excess logging taking up disk space. > > Thank you > > ... > [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64956. > [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64957 of user root. > [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64957. > [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64958 of user root. > [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64958. > [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64959 of user root. > [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64959. > [Wed Nov 13 04:18:01 2019] elogind[2278]: New session 64969 of user root. > [Wed Nov 13 04:18:01 2019] elogind[2278]: Removed session 64969. > [Wed Nov 13 04:18:01 2019] elogind[2278]: New session 64970 of user root. > [Wed Nov 13 04:18:01 2019] elogind[2278]: Removed session 64970. > [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64971 of user root. > [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64971. > [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64972 of user root. > [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64972. > [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64973 of user root. > [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64973. That is 6 new root sessions in 2 seconds. What is in your cron job? I can't immediately think of a reason why you would want a logind session for a root cron job at all. Mark ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] disable elogind messages?
Hi, Any way to disable elogind from filling up the message logs? I think all these messages are happening because I have cron jobs running frequently. I could possibly tell rsyslog to file these in cron.log (if it is cron) but there is still the problem of excess logging taking up disk space. Thank you ... [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64956. [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64957 of user root. [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64957. [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64958 of user root. [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64958. [Wed Nov 13 04:15:01 2019] elogind[2278]: New session 64959 of user root. [Wed Nov 13 04:15:01 2019] elogind[2278]: Removed session 64959. [Wed Nov 13 04:18:01 2019] elogind[2278]: New session 64969 of user root. [Wed Nov 13 04:18:01 2019] elogind[2278]: Removed session 64969. [Wed Nov 13 04:18:01 2019] elogind[2278]: New session 64970 of user root. [Wed Nov 13 04:18:01 2019] elogind[2278]: Removed session 64970. [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64971 of user root. [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64971. [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64972 of user root. [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64972. [Wed Nov 13 04:18:02 2019] elogind[2278]: New session 64973 of user root. [Wed Nov 13 04:18:02 2019] elogind[2278]: Removed session 64973. [Wed Nov 13 04:21:01 2019] elogind[2278]: New session 64983 of user root. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
