On 2015-10-14 04:24, David C. Rankin wrote:
On 10/13/2015 11:46 AM, Andrei Borzenkov wrote:
This is the *EXACT* reason for your logs filling up. Enable it and errors will go away.
No, that is incorrect, it just fills my logs with different messages. Why do you think I started looking for a way to turn the damn thing off to begin with. The modem is not compatible with modem manager and it cannot find a compatible USB device when it is running, so I get those messages instead.
Then filter them out. In "/etc/rsyslog.conf" I have: if ($programname startswith 'org.gtk.' and $msg contains '### debug:') or ($programname startswith 'org.gtk.vfs.Daemon') or ($programname startswith 'org.freedesktop. Tracker1') \ or ($programname startswith 'org.gnome.evince.Daemon' and ($msg contains 'egisterDocument' or $msg contains 'Watch name')) \ or ($programname startswith 'org.gnome.zeitgeist.Engine') \ or ($programname startswith 'org.xfce.FileManager' and ($msg contains 'fixme:' )) \ or ($programname == 'systemd' and ($msg contains 'Failed to open private bus connection: Failed to connect to socket' )) \ then -/var/log/pruned & stop if ($syslogfacility-text == 'mail') and ($programname == 'spamd' or $syslogtag == '[spamd]:') and \ ($msg contains_i 'Use of each() on hash after insertion without resetting hash iterator results in undefined behavior') \ then -/var/log/pruned.warn & stop You would need something like, before the entries for warn and messages: # 2015-10-12T01:49:35.685011-05:00 alchemy dbus[594]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service' # 2015-10-12T01:49:35.686490-05:00 alchemy dbus[594]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory. if ($programname == 'dbus' and $syslogtag == '[system]:') and \ ($msg contains_i 'Activation via systemd') and ($msg contains_i 'dbus-org.freedesktop.ModemManager1.service') \ then -/var/log/pruned & stop Test it via: #CER: Test config by using # rsyslogd -N 2 -f /etc/rsyslog.conf # Then restart service (reload is not enough) Warning: sometimes rules fail and it is impossible to find out why. rsyslog has terrible syntax error reporting, IMO. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)