From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-user+bounces-162318-garchives=archives.gentoo.org@lists.gentoo.org> Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 97D5D138A87 for <garchives@archives.gentoo.org>; Mon, 23 Feb 2015 08:15:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BCBA1E08AD; Mon, 23 Feb 2015 08:15:38 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4C223E089D for <gentoo-user@lists.gentoo.org>; Mon, 23 Feb 2015 08:15:37 +0000 (UTC) Received: from marcec.fritz.box ([93.181.44.4]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M5tU1-1XbIxa2wX3-00xqQZ for <gentoo-user@lists.gentoo.org>; Mon, 23 Feb 2015 09:15:35 +0100 Date: Mon, 23 Feb 2015 09:15:29 +0100 From: Marc Joliet <marcec@gmx.de> To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] syslog-ng: how to read the log files Message-ID: <20150223091529.656c0008@marcec.fritz.box> In-Reply-To: <87vbitldj5.fsf@heimdali.yagibdah.de> References: <87lhjws8ci.fsf@heimdali.yagibdah.de> <CAJ1xhMW7xLROrgcz+iuNUvSVSt6x7AZ6i_L8G6ab7Ux3hJg4wA@mail.gmail.com> <28267.1424201355@ccs.covici.com> <87d257q7en.fsf@heimdali.yagibdah.de> <20150218223115.7fb56f66@digimed.co.uk> <87vbitldj5.fsf@heimdali.yagibdah.de> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/DWm3fuFJ6FFon1fa63ilc2j"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:MdpZmNJVxE1K4gn4zKwtwZtFoMnbGjz7chgcDwZONHYEXnvLSHp geN4UNGlcpOaKEOip5gCShjRO2axyV8tWxH1hC4nzRLqOF/mLWJ0wgeN/4txy+MR97t8Fet eGfs8ddu8I+DzLsKOgCnbDOl+gX3XGEw3S3xHQ+jnKpJcDfkw0gW2dY5bvR6L+nMnrTekUP Y4/qFeRaV9D9tjDfUHL0w== X-UI-Out-Filterresults: notjunk:1; X-Archives-Salt: fc8496aa-aa00-4bc7-9036-ca2a536cbaad X-Archives-Hash: 0653a95c66cef30fbbcad578f81f90e0 --Sig_/DWm3fuFJ6FFon1fa63ilc2j Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 23 Feb 2015 00:41:50 +0100 schrieb lee <lee@yagibdah.de>: > Neil Bothwick <neil@digimed.co.uk> writes: >=20 > > On Wed, 18 Feb 2015 21:49:54 +0100, lee wrote: > > > >> > I wonder if the OP is using systemd and trying to read the journal > >> > files? =20 > >>=20 > >> Nooo, I hate systemd ... > >>=20 > >> What good are log files you can't read? > > > > You can't read syslog-ng log files without some reading software, usual= ly > > a combination of cat, grep and less. systemd does it all with journalct= l. > > > > There are good reasons to not use systemd, this isn't one of them. >=20 > To me it is one of the good reasons, and an important one. Plain text > can usually always be read without further ado, be it from rescue > systems you booted or with software available on different operating > systems. It can be also be processed with scripts and sent as email. > You can probably even read it on your cell phone. You can still read > log files that were created 20 years ago when they are plain text. >=20 > Can you do all that with the binary files created by systemd? I can't > even read them on a working system. What Canek and Rich already said is good, but I'll just add this: it's not = like you can't run a classic syslog implementation alongside the systemd journal. On my systems, by *default*, syslog-ng kept working as usual, getting the l= ogs from the systemd journal. If you want to go further, you can even configure the journal to not store logs permanently, so that you *only* end up with plain-text logs on your system (Duncan on gentoo-amd64 went this way). So no, the format that the systemd journal uses is most decidedly *not* a r= eason against using systemd. Personally, I'm probably going to uninstall syslog-ng, because journalctl is *such* a nice way to read logs, so why run something whose output I'll never read again? I recommend reading http://0pointer.net/blog/projects/journalctl.html for examples of the kind = of stuff you can do that would be cumbersome, if not *impossible* with regular syslog. HTH --=20 Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup --Sig_/DWm3fuFJ6FFon1fa63ilc2j Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJU6uGmAAoJEL/Q5oYsiHj0ZyQQAIvs6WUko3Rxoz/5ZfZW//U4 k9NXuuGZi0aHD5f/pxRMXuqWxJENfY4RjiyIRv+1RsS9DS133qHCdmzmbpYQ2unl 9nW66+AZj3sJuTFhdIxq7n8SWw3cUweKhPS9hBPDZLc+XOJNWSvPFBIVWD7QqRGD 4uuLsAsZ6rdqq+YzI2Vf1xbYJpaE6J0zyc2NIgffyHP67fEOqKXk6WPszAhpwCiF 8sT9xxUe78ok0O31Rn71S+ksHtISNByHAKb2Nq8S8bv1i8rGe3h9R3kTzWe1DyTQ aUPW+moj+qwQVvVkfJQeoukSXK0aFqa1aSvBMSN1FJ3opqPO8+lUwxkIVZCbGfM1 xq6SYor6C69xFDUcOG1qz8J+sDlTSHylHa3icCcPTKIX6cDk6ZTj9rWMfu3oRZRb zbXt7sdKFOSFhHvASGDXzruyOZCI2wh0gJRc0xHRcIzp1sUz3PQjiJySegEUrrCI jjXZ9Z0nlEppUyY8+NG7efwcSc595Dxc2k6Lz5e2qd8uZqqvXYiBKxozmzMsP494 xZ+/HBkYmD2GTCJ1Y7skN8zoD6K8qXBLRPVwAkfcFPBm1vmQLmOE/jgVTsPLkHgC gLe5LYBt520OBhiQ7QDorYzcgCc6bJ8lviI6wwvhgVr65FoyyNls4cEfhdivmT3J /GjTQA4+LHlmrGUZ+lCg =Tg2r -----END PGP SIGNATURE----- --Sig_/DWm3fuFJ6FFon1fa63ilc2j--