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 F1137138A1A for ; Tue, 17 Feb 2015 19:46:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1D8C5E083E; Tue, 17 Feb 2015 19:46:01 +0000 (UTC) Received: from mail-la0-f41.google.com (mail-la0-f41.google.com [209.85.215.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C4BCFE0804 for ; Tue, 17 Feb 2015 19:45:59 +0000 (UTC) Received: by lams18 with SMTP id s18so37951709lam.13 for ; Tue, 17 Feb 2015 11:45:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=D0cpGtLWBT8yywtc2IOLlZJutIybfou++AnqHPmdAH4=; b=ED4wT89YzrK4BEZPv8kTR1MoeHGfEqS6scVmbvHTinqLwdHFtCM4JvZCwPKPRaUNha GH8O1S7QEKoddlgNrCTQFM2AJoP5AQmiSHEcDYHy89mFR5w3RihTpAhwSEmp92BKKv9Q 2HZNvBYTuL6GiTHrjC+0edeJi12HOR/ufeA14qx+P4X1EI8Gt4qPcZquCRj6Yp0mrYZI 53jicXBnK+D9UzsiWZiPkgUmdfixP/XoXke2m51A2ac66Rus8U3qXEFWFiZ2x7DcnZtZ GmPC6gZvkiXqCbwsRLAYG903ZFJh9YwKvzSUNIucuDFwM8LT2T1y/5/cgqQzX8+SUuR/ l38A== X-Received: by 10.152.161.232 with SMTP id xv8mr30520010lab.15.1424202358304; Tue, 17 Feb 2015 11:45:58 -0800 (PST) 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 Received: by 10.114.77.38 with HTTP; Tue, 17 Feb 2015 11:45:38 -0800 (PST) In-Reply-To: <28267.1424201355@ccs.covici.com> References: <87lhjws8ci.fsf@heimdali.yagibdah.de> <28267.1424201355@ccs.covici.com> From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= Date: Tue, 17 Feb 2015 13:45:38 -0600 Message-ID: Subject: Re: [gentoo-user] syslog-ng: how to read the log files To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a113461f2a7b621050f4df333 X-Archives-Salt: cc112c19-31fd-4208-a8c4-56569c3e08a7 X-Archives-Hash: 71810afce4fbb0a680ab9d72f68bf514 --001a113461f2a7b621050f4df333 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Feb 17, 2015 at 2:29 PM, wrote: > > Alexander Kapshuk wrote: > > > On Tue, Feb 17, 2015 at 8:26 PM, lee wrote: > > > > > Hi, > > > > > > how do you read the log files when using syslog-ng? > > > > > > The log file seem to be some sort of binary that doesn't display too > > > well in less, and there doesn't seem to be any way to read them. > > > > > > > > > -- > > > Again we must be afraid of speaking of daemons for fear that daemons > > > might swallow us. Finally, this fear has become reasonable. > > > > > > > > If you're talking about /var/log/messages, which is: > > messages: data > > > > I use cat(1). > > I wonder if the OP is using systemd and trying to read the journal > files? Those live under /var/lib/journal (which you need to create; Gentoo doesn't do it by default last time I saw), in the directory named after the machine ID (cat /etc/machine-id). And there are several journal files, of the kind: system@1df50cd49c7f4a089c9414561f65aac7-000000000006f091-000507235df68768.j= ournal I think it would be really difficult to mix up that with /var/log/messages. I think it's just that some part of /var/log/messages got corrupted (happens a lot of times), and therefore /usr/bin/less identifies it as a binary files since it contains non-printable characters. Regards. -- Canek Pel=C3=A1ez Vald=C3=A9s Profesor de asignatura, Facultad de Ciencias Universidad Nacional Aut=C3=B3noma de M=C3=A9xico --001a113461f2a7b621050f4df333 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Tue, Feb 17, 2015 at 2:29 PM, <covici@ccs.covici.com> wrote:
>
> Al= exander Kapshuk <alexande= r.kapshuk@gmail.com> wrote:
>
> > On Tue, Feb 17, 201= 5 at 8:26 PM, lee <lee@yagibdah.de> wrote:
> >
> > > Hi,
> > >
> &= gt; > how do you read the log files when using syslog-ng?
> > &= gt;
> > > The log file seem to be some sort of binary that does= n't display too
> > > well in less, and there doesn't s= eem to be any way to read them.
> > >
> > >
>= > > --
> > > Again we must be afraid of speaking of daem= ons for fear that daemons
> > > might swallow us.=C2=A0 Finally= , this fear has become reasonable.
> > >
> > >
&= gt; > If you're talking about /var/log/messages, which is:
> &= gt; messages: data
> >
> > I use cat(1).
>
> = I wonder if the OP is using systemd and trying to read the journal
> = files?

Those live under /var/lib/journal (which you need to create; = Gentoo doesn't do it by default last time I saw), in the directory name= d after the machine ID (cat /etc/machine-id). And there are several journal= files, of the kind:

system@1df50cd49c7f4a089c9414561f65= aac7-000000000006f091-000507235df68768.journal

I thi= nk it would be really difficult to mix up that with /var/log/messages.

I think it's just that some part of=C2=A0/var/log/= messages got corrupted (happens a lot of times), and therefore /usr/bin/les= s identifies it as a binary files since it contains non-printable character= s.

Regards.
--
Canek Pel=C3=A1ez Vald=C3=A9s
Profesor de as= ignatura, Facultad de Ciencias
Universidad Nacional Aut=C3=B3noma de M= =C3=A9xico
--001a113461f2a7b621050f4df333--