Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Argument: journald is more complex than syslogd, and complexity is evil!
Proposal: use the simpler syslogd and then add complex and error-prone log parsing toolkits to get 70% of the features of journald at 200% the complexity cost.
Rationale: Pulseaudio was buggy a couple years ago.
That newfangled Journal thing
Posted Nov 30, 2011 23:26 UTC (Wed) by dlang (✭ supporter ✭, #313)
he's 'solving' a problem that isn't really there, and he doesn't actually solve the stated problem.
Also, please point out anywhere that I have said anything about pulseaudio.
Posted Nov 30, 2011 23:34 UTC (Wed) by anselm (subscriber, #2796)
Read the <expletive> proposal. Journald isn't just about the hashes.
Posted Nov 30, 2011 23:44 UTC (Wed) by dlang (✭ supporter ✭, #313)
if you want to ignore the hashes part of things, we can talk about the structured log part of things. logs are only as structured as the programmer creating them makes them, if you have a super-detailed log structure available and the programmer creates a field "details" type "string" and puts everything into that field it is going to be just as unstructured as syslog traditionally has been.
He ignores or is ignorant of recent standards in syslog (some of which go back quite a few years)
he has a few new ideas buried in the proposal, but they are so overshadowed by misstatements and 'solutions' to problems that already have documented, standardized solutions (that are not compatible with the proposed solution other than running logging services in parallel) that it undermines the entire proposal
Posted Dec 1, 2011 17:03 UTC (Thu) by kh (subscriber, #19413)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds