From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 04872138A1F for ; Thu, 18 Sep 2014 03:11:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EC27AE0B6F; Thu, 18 Sep 2014 03:10:54 +0000 (UTC) Received: from mail-ig0-f195.google.com (mail-ig0-f195.google.com [209.85.213.195]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 82C79E0B5F for ; Thu, 18 Sep 2014 03:10:53 +0000 (UTC) Received: by mail-ig0-f195.google.com with SMTP id uq10so105637igb.2 for ; Wed, 17 Sep 2014 20:10:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=1lzXoazNjw3hYU00cGsalM1YEFojRfBLAd+QyQ60Fwg=; b=pUR0oNbeepZITJ5i0YWxHV6Rqmp1ReIVOzkCWZXXrIxsVIVWKPZG+DaLNLa1l/asfS s/XgKGi9Bm+fmIxYMUVhy1Sb24oQr3SjL3iNOBuoqSuiEXhvB2ptjqwwE4SbEA4whdLA 7pbfkB5RroTbtPUsR55cdMWDS02YvR9wdJDxWXZe1VxqN6OTClZP9jJXiAy/r6iES3a1 iGdue8+PFJe4xMpceKKfN90Ui59081C7cF67ZGX61ZNUFzNKylf/8qI83r8SCciCpXst 3W7Gt6r+BlKZrup5SFh3ZoEw5iMZ1rXGjMm6xXGKAHgKWUGLhLMC/uzjdSjSi4ipq6IR Iwgw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.43.0.133 with SMTP id nm5mr9571304icb.55.1411009852714; Wed, 17 Sep 2014 20:10:52 -0700 (PDT) Received: by 10.50.227.39 with HTTP; Wed, 17 Sep 2014 20:10:52 -0700 (PDT) In-Reply-To: References: Date: Thu, 18 Sep 2014 11:10:52 +0800 Message-ID: Subject: Re: [gentoo-user] Is systemd-journald a complete replacement for sysklogd? From: Mark David Dumlao To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=bcaec50fe0630bb71a05034e559e X-Archives-Salt: 75f36ee5-d9c7-4874-a5b8-ec54cc171085 X-Archives-Hash: 3dd3a7027debcfd064d46e5eabe51329 --bcaec50fe0630bb71a05034e559e Content-Type: text/plain; charset=UTF-8 It is, but. You'll have to get used to running and searching via journalctl instead of processing the logs directly. Journal is not persistent across reboots by default, but you can reconfigure it to be. (just create /var/log/journal) Last I recall you won't get fine-grained per-daemon space controls on the logs, just a system-wide size and retention time for all journal entries. Usually that's enough, but if all else fails you can fallback to another logger. On Thu, Sep 18, 2014 at 10:56 AM, walt wrote: > I'm trying to track down a bad bug in dhcpcd-6.4.4, so (unlike most days > ;) I'm > paying close attention to the output of journalctl. > > The confusing part is that the output of journalctl is *very* different > depending > on whether dhcpcd starts correctly during boot. Or not. > > I think I may be shooting myself in the usual foot by continuing to use > sysklogd > along with systemd (using my own custom *.service script to start > sysklogd). > > If journald is really a complete syslog replacement then I'll dump my old > kludge > and be very happy to do it. > > Canek, maybe? Anyone? > > > > > -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none --bcaec50fe0630bb71a05034e559e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is, but.

You'll ha= ve to get used to running and searching via journalctl instead of processin= g the logs directly.
Journal is not persistent across reboots by d= efault, but you can reconfigure it to be. (just create /var/log/journal)
Last I recall you won't get fine-grained per-daemon space contro= ls on the logs, just a system-wide size and retention time for all journal = entries.

Usually that's enough, but if all else fails you = can fallback to another logger.

On Thu, Sep 18, 2014 at 10:56 AM, walt <w41ter@gmai= l.com> wrote:
I'm tryin= g to track down a bad bug in dhcpcd-6.4.4, so (unlike most days ;) I'm<= br> paying close attention to the output of journalctl.

The confusing part is that the output of journalctl is *very* different dep= ending
on whether dhcpcd starts correctly during boot. Or not.

I think I may be shooting myself in the usual foot by continuing to use sys= klogd
along with systemd (using my own custom *.service script to start sysklogd)= .

If journald is really a complete syslog replacement then I'll dump my o= ld kludge
and be very happy to do it.

Canek, maybe?=C2=A0 Anyone?







--
This email is:=C2=A0 = =C2=A0 [ ] actionable=C2=A0=C2=A0 [ ] fyi=C2=A0 =C2=A0 =C2=A0 =C2=A0 [ ] so= cial
Response needed:=C2=A0 [ ] yes=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [ = ] up to you=C2=A0 [ ] no
Time-sensitive:=C2=A0=C2=A0 [ ] immediate=C2= =A0 =C2=A0 [ ] soon=C2=A0 =C2=A0 =C2=A0=C2=A0 [ ] none --bcaec50fe0630bb71a05034e559e--