Hi there, On 02/11/2015 02:16 PM, Anselm Lingnau wrote: > Simone Piccardi <[email protected]> wrote: > >> Could you provide some examples? In my (limited) experience almost all >> programs I'm using just log to text file (journald beeing the main >> exception). > Apache can write its access log to an SQL database, for example. AFAIK, > the modern syslog replacements (like rsyslogd or syslogd-ng) can also be > configured to use an SQL database backend rather than the traditional > text files. Reasons why one would want to do this include (a) speed and > (b) ease of finding things, both of which aren't exactly among the > strengths of the text-file based approach (as the journald developers, > too, are fond of pointing out). > > Note that getting these tools to actually log to an SQL database is not > part of the LPIC-1 exam (and rightly so, as far as I'm concerned). I > presume the general idea is that a “junior” sysadmin might end up > working in a place where senior staff have set things up that way, and a > junior employee would need basic familiarity with SQL in order to look > at logging data – much like LPIC-1 doesn't require a candidate to be > able to install and configure an MTA from scratch, just to deal with it > once it's there.
As this is usually not the default I wouldn't expect many people really using it. If, on the other hand, someone touches these defaults, than it would be most likely to implement tools like logstash to centrally log, normalize, aggregate and analyze the log data. This, however, would be far beyond the LPIC-1 focus.In case someone would have set this up the junior administrator would find himself in front of an interface like kibana which requires some additional learning time anyway. > Anyway, that's what I was told at the time. Maybe Matt can shed more > light on the actual rationale of adding SQL to LPIC-1. After all, he was > there and I wasn't ;^). The way LPI figures out exam objectives does > suggest that the issue must have come up during the JTA. Would be interesting to know where this objective's roots are, yeah :-) This objective has already been marked in the "Future consideration" section of the LPIC-1 wiki page, so it will for sure pop up again during the next review of the objectives. Fabian (who would still vote for dropping SQL once we get the chance to) _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
