Bugzilla – Bug 928682
Screenfuls of annoying drivel, mostly from audit
Last modified: 2015-04-28 15:54:38 UTC
This is a console login: ------------------------------------ Welcome to openSUSE 20150413 "Tumbleweed" - Kernel 3.19.3-1-default (ttyS0). linux login: root [ 232.020794] audit: type=1130 audit(1430113524.707:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sshd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 232.134526] audit: type=1129 audit(1430113524.817:48): pid=8012 uid=0 auid=4294967295 ses=4294967295 msg='old-level=N new-level=5 comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success' [ 232.178095] audit: type=1130 audit(1430113524.862:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 232.205800] audit: type=1131 audit(1430113524.892:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ------------------------------------ It's a newly installed system that needs to be configured. In between the drivel one can just find the important lines. Editing e.g. /etc/fstab with joe in a console window is not the time being annoyed by a screen full of useless poop. It's ridiculous and makes real work almost impossible. This is with cubieboard armv7 factory build 293.8 serial port console but I have observed the same in oS 13.2 x86 on the local consoles or when logged in via ssh. Dumping all that stuff into /var/log/apparmor-warn would be good, being prevented from getting any work done by screenfuls of rubbish is neither appreciated nor useful, especially when I at that point have no intention of using apparmor until later.
Hi Tony, I'm not quite sure whether it is right to assign it to you, please feel free to reassign whenever necessary, thank you!
Duplicate. *** This bug has been marked as a duplicate of bug 860778 ***