Am 22.09.2014 um 16:25 schrieb Miloslav Trmač: > (stripping systemd-devel) > > ----- Original Message ----- >> Am 22.09.2014 um 14:44 schrieb Jóhann B. Guðmundsson: >>> This is simply untrue as "journalctl -o export" will show you. >> >> where is it in the message? >> the process is "systemd" >> >> how to distinct between user sessions and systemn boot? >> ":programname" don't work and ":msg, startswith" don't work >> >> Mar 18 23:01:01 rawhide systemd[577]: Stopped target Default. >> Mar 18 23:01:01 rawhide systemd[577]: Stopping Basic System. >> Mar 18 23:01:01 rawhide systemd[577]: Stopped target Basic System. >> Mar 18 23:01:01 rawhide systemd[577]: Stopping Paths. > > In Fedora’s default configuration, in addition to the traditional rsyslog fields, > all journal fields are available in rsyslog. Would filtering for $_PID being, > or not being, 1, help? possibly yes but i am still concerned that it is the wrong way to add each year new rules to filter and drop a growing amount of messages which should not exist in a non-debugging environment * they produce load twcie (generate and filter) * they lead to rotate the in memory journal more often * nobody knows what a later release adds which falls in "systemd but not PID1" and would also be stripped * the real solution has to be adressed upstream: reduce verbose level on a normal installation and create the noise only in debug levels i really don't get why other software for decades knows different log levels (informational, only warn, only critical errors) and just systemd needs to go they way of "produce anything always" that's hardly the attitude demanding long year users of Linux systems to be all time friendly and nice when you day for day give them the feeling of no care
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
