From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syslog-ng: how to read the log files
Date: Thu, 19 Feb 2015 14:02:06 -0500 [thread overview]
Message-ID: <2735744.Vs3r9ZmJIO@acer> (raw)
In-Reply-To: <87lhjws8ci.fsf@heimdali.yagibdah.de>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On Tuesday, February 17, 2015 7:26:05 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.
>
>
>
You can just pipe the output of strings /var/log/messages to less. You can use
strings(1) for systemd journal files also.
--
Fernando Rodriguez
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-19 19:04 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 18:26 [gentoo-user] syslog-ng: how to read the log files lee
2015-02-17 18:37 ` Rich Freeman
2015-02-17 18:38 ` Alexander Kapshuk
2015-02-17 19:09 ` Alexander Kapshuk
2015-02-17 19:29 ` covici
2015-02-17 19:45 ` Canek Peláez Valdés
2015-02-17 22:31 ` Marc Joliet
2015-02-18 19:01 ` systemd journal location (was: Re: [gentoo-user] syslog-ng: how to read the log files) Marc Joliet
2015-02-18 18:22 ` [gentoo-user] syslog-ng: how to read the log files gottlieb
2015-02-18 18:53 ` Canek Peláez Valdés
2015-02-18 22:43 ` gottlieb
2015-02-18 20:49 ` lee
2015-02-18 22:31 ` Neil Bothwick
2015-02-22 23:41 ` lee
2015-02-23 0:19 ` Canek Peláez Valdés
2015-05-04 5:57 ` lee
2015-05-04 14:56 ` Tom H
2015-05-09 15:01 ` lee
2015-05-09 16:00 ` Peter Humphrey
2015-02-23 0:37 ` Rich Freeman
2015-05-04 6:09 ` lee
2015-02-23 8:15 ` Marc Joliet
2015-02-23 8:41 ` covici
2015-02-23 16:18 ` Canek Peláez Valdés
2015-02-23 17:49 ` covici
2015-02-23 18:10 ` Canek Peláez Valdés
2015-02-23 19:19 ` Marc Joliet
2015-02-23 19:31 ` covici
2015-02-23 19:35 ` Canek Peláez Valdés
2015-02-23 20:07 ` covici
2015-02-23 23:18 ` covici
2015-02-23 23:29 ` Neil Bothwick
2015-02-24 0:50 ` Peter Humphrey
2015-02-24 7:21 ` Marc Joliet
2015-02-24 9:57 ` Matti Nykyri
2015-02-23 19:26 ` covici
2015-05-04 6:14 ` lee
2015-05-04 11:24 ` Rich Freeman
2015-05-09 15:08 ` lee
2015-05-09 18:07 ` Rich Freeman
2015-05-10 17:51 ` [gentoo-user] " »Q«
2015-02-17 18:41 ` [gentoo-user] " Matti Nykyri
2015-02-17 22:51 ` Peter Humphrey
2015-02-17 23:13 ` Peter Humphrey
2015-02-17 23:23 ` Jan Sever
2015-02-17 23:54 ` Peter Humphrey
2015-02-18 7:38 ` Mick
2015-02-18 9:38 ` Peter Humphrey
2015-02-17 23:52 ` Rich Freeman
2015-02-17 23:55 ` Peter Humphrey
2015-02-17 19:02 ` [gentoo-user] " Nikos Chantziaras
2015-02-17 19:02 ` [gentoo-user] " Alan Mackenzie
2015-02-17 19:17 ` lee
2015-02-17 22:01 ` Mick
2015-02-18 13:29 ` Stroller
2015-02-18 20:40 ` lee
2015-02-18 21:33 ` Stroller
2015-02-22 23:48 ` lee
2015-02-23 0:21 ` Canek Peláez Valdés
2015-02-23 2:57 ` Dale
2015-02-23 3:06 ` Peter Humphrey
2015-02-23 4:28 ` Dale
2015-02-23 10:13 ` Peter Humphrey
2015-02-24 19:30 ` Stroller
2015-02-19 19:02 ` Fernando Rodriguez [this message]
2015-02-19 19:11 ` Jan Sever
2015-02-23 0:03 ` lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2735744.Vs3r9ZmJIO@acer \
--to=frodriguez.developer@outlook.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox