| |||||||||||||
Distribution quotes of the weekDistribution quotes of the weekPosted Oct 19, 2012 10:57 UTC (Fri) by nix (subscriber, #2304)Parent article: Distribution quotes of the week
For F19 I plan to submit a feature asking for not installing syslog by default anymore.... he's serious. Gosh it's a good thing nobody has scripts or programs that parse logfiles, isn't it. Oh wait. (Though he doesn't recommend removing it. Yet.)
(Log in to post comments)
Distribution quotes of the week Posted Oct 19, 2012 15:15 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link]
Journal is pixel-perfectly compatible with syslogd, so your scripts would work fine with it.
Distribution quotes of the week Posted Oct 19, 2012 18:26 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
This is the first that I've heard of this.
Since it's rsyslog that's being removed, how much of the rsyslog.conf and rsyslog.d/*.conf will Journal understand?
My understanding was that the Journal authors were claiming that you could feed the data into the journal with syslog tools, but that accessing the data required new tools (due to all the new capabilities that the journal introduced), and that the files created were in a new, binary format to support the new anti-modification stuff (among other things)
Distribution quotes of the week Posted Oct 19, 2012 18:56 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link]
Journal doesn't understand rsyslog's config, but it outputs syslog in exactly the same format by default (by design).
Distribution quotes of the week Posted Oct 19, 2012 19:13 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
If it doesn't understand the configs, how does it tell which logs to output to which files?
Or is all this just hard-coded somewhere to match the Fedora default?
With rsyslog, .rpm packages could drop .conf files into /etc/rsyslog.d to provide package specific configs.
|
|||||||||||||