On Thu, February 20, 2014 06:24, Canek Peláez Valdés wrote: > On Wed, Feb 19, 2014 at 2:50 AM, J. Roeleveld <jo...@antarean.org> wrote: >> On Tue, February 18, 2014 15:37, Canek Peláez Valdés wrote: >>> On Tue, Feb 18, 2014 at 3:54 AM, J. Roeleveld <jo...@antarean.org> >>> wrote:
<snipped> >> Same question applies, can I disable these code-paths during >> compile-time? > > No you can't; if you wanted the journal to work exactly as rsyslog (or > syslog-ng), then there is no reason to use the journal. Its raison > d'être is the new features it brings. > > If you don't want those features, don't use the journal. Which means, don't use systemd, as it's all or nothing there. >> I do not see the need to have to spend time to change working code to be >> able to handle different formats. > > Well, I prefer it when someone does the work for me. So do I, but I doubt the systemd developers are willing to change all my scripts and monitoring tools to work with systemd. >> Additionally, the use of "tail -f" and "grep" allows me to check the >> logs >> real-time for debugging purposes. > > journalctl -f > > Checks the logs in real time. Again, [1]. > >> Having to use a seperate tool that converts some proprietary binary >> format >> to human readable/scriptable single-line logs makes no sense. > > Its not proprietary; the source code is available, you can write your > own parser if you want. The binary format is to be able to do O(log n) > searches, that's it. It's a performance optimization. The specification for Office Open XML is also available. I do not see Libreoffice or Openoffice properly supporting that yet either, even though there is great demand and a large development team (with sufficient financing) available. >> It all sounds too much like the MS Windows Event-viewer to me. > > Never used it. It's a binary, indexed logging system that is part of the OS. Sounds similar to journald. >> Too many events with no usefull logging information (And I am referring >> to >> OS-level messages as to why default services are not starting) > > systemctl status apache2.service > > (see [2]) will print the status of the Apache web server, and also the > last lines from the logs. You can control how many lines. You can > check also with the journal, as I showed up. /etc/init.d/apache2 status will also tell me if it is running. And which logs? On a host with only 1 domain pointing to it, I have 6 logfiles for apache. And that is the default configuration. And what I was referring to was the useless info found in the event-log for services that are not written to actually use it. -- Joost
