Fedora 21 Server and log-flooding
Stephen Gallagher
sgallagh at redhat.com
Wed May 28 13:17:08 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/27/2014 08:30 AM, Reindl Harald wrote:
> maybe someone of the server SIG could try to explain the
> systemd-maintainers that calculation and that this is unacceptable
> on real-world servers because it burries any interesting
> information
>
> the way systemd in Rawhide now logs make it unacceptable on
> production servers and that said from someone running Fedora on a
> lot of real-world servers for 6 years now
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1072368#c8
>
> if the "Stopping", "Stopped", "Removed", "Starting" and "Reached"
> messages would only have a prefix to filter them out with rsyslog,
> currently you can't distinct them between system-wide messages
>
> such flooing up to a self-DOS belongs in a debug level
It seems to me that a more useful (and generic) solution to this would
be to create a rules-engine for specifying what messages get sent
through the syslog output (and if sent, optionally prefixed).
The internal journal message containing these start/stop notifications
have a number of useful structuring elements that would make it easy
to filter on, if such a rules engine was devised.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlOF4dQACgkQeiVVYja6o6MXSACfXmqfDK17YrRNg81YMppyBklu
HTgAnjBqHWp84INpHreKZfCXln84P8c+
=oJfS
-----END PGP SIGNATURE-----
More information about the server
mailing list