Bug 770014 - systemd-logind is heavily spamming logs when cron jobs are running
Summary: systemd-logind is heavily spamming logs when cron jobs are running
Keywords:
Status: CLOSED DUPLICATE of bug 727315
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-23 02:33 UTC by Michal Jaegermann
Modified: 2011-12-23 21:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-12-23 21:08:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Jaegermann 2011-12-23 02:33:28 UTC
Description of problem:

With every cron job systemd-logind writes quite useless information in /var/log/messages.  The net effect is that on a machine which runs often some small cron jobs logs are flooded by stuff like that:

Dec 22 19:04:01 ... systemd-logind[1037]: New session 943 of user root. 
Dec 22 19:04:01 ... systemd-logind[1037]: Removed session 943.
Dec 22 19:06:01 ... systemd-logind[1037]: New session 944 of user root. 
Dec 22 19:06:01 ... systemd-logind[1037]: Removed session 944.

This not only makes logs hard to read but is really a security issue if one would try to identify a needle of an unexpected root session in this haystack. Is there any way to stop this garbage? 'man systemd-logind.conf' does not seem to suggest any methods to restrain this deluge (save killing logging, of course, but this is not an accptable solution).

Version-Release number of selected component (if applicable):
systemd-37-3.fc16

How reproducible:
always

Comment 1 Michal Schmidt 2011-12-23 21:08:56 UTC

*** This bug has been marked as a duplicate of bug 727315 ***


Note You need to log in before you can comment on or make changes to this bug.