On Mon, Nov 25, 2013 at 12:58 AM, Frantisek Hanzlik fra...@hanzlici.cz wrote:
Frank Murphy wrote:
On Sun, 17 Nov 2013 12:37:03 +0100
Patrick Lists fedora-l...@puzzled.xs4all.nl wrote:
I meant the transmission of the log to another log server. Not the
log itself. Anyway, here is Lennart
Frank Murphy wrote:
On Sun, 17 Nov 2013 12:37:03 +0100
Patrick Lists fedora-l...@puzzled.xs4all.nl wrote:
I meant the transmission of the log to another log server. Not the
log itself. Anyway, here is Lennart Poettering's rationale behind
journald:
One of the things you will see after
Hi Jonas,
I have a comment, and a question.
On Sun, Nov 17, 2013 at 03:46:55PM +0200, Joonas Sarajärvi wrote:
2013/11/17 Frantisek Hanzlik fra...@hanzlici.cz:
It was mean mainly from administrator view. When things go bad,
machine HW/SW fail or any other disasters occurs, logs are very
On Mon, Nov 18, 2013 at 3:14 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
I have been very frustrated with journalctl. The manual page is very
unhelpful in that regard. For example the other day, I wanted to
investigate why my laptop shutdown suddenly (I think it was
overheating), but
On Mon, Nov 18, 2013 at 03:43:57PM +, Tom H wrote:
On Mon, Nov 18, 2013 at 3:14 PM, Suvayu Ali fatkasuvayu+li...@gmail.com
wrote:
I have been very frustrated with journalctl. The manual page is very
unhelpful in that regard. For example the other day, I wanted to
investigate why my
On Mon, Nov 18, 2013 at 4:41 PM, Suvayu Ali fatkasuvayu+li...@gmail.com wrote:
On Mon, Nov 18, 2013 at 03:43:57PM +, Tom H wrote:
On Mon, Nov 18, 2013 at 3:14 PM, Suvayu Ali fatkasuvayu+li...@gmail.com
wrote:
I have been very frustrated with journalctl. The manual page is very
unhelpful
2013/11/18 Suvayu Ali fatkasuvayu+li...@gmail.com:
Hi Jonas,
I have a comment, and a question.
On Sun, Nov 17, 2013 at 03:46:55PM +0200, Joonas Sarajärvi wrote:
The journald log format is documented at least to some extent [1], and
there exists free software for reading the log. To me, it
Sorry for posting again so soon and replying to myself, but I just
noticed one very useful thing that might help quite much in the
specific problem you described:
2013/11/18 Joonas Sarajärvi m...@iki.fi:
2013/11/18 Suvayu Ali fatkasuvayu+li...@gmail.com:
the other day, I wanted to
investigate
On Mon, Nov 18, 2013 at 04:48:32PM +1030, Tim wrote:
Tim:
And if logs are in a format that you cannot read, you cannot safely
submit them to an outside server. You don't know what they contain.
Logon credentials, confidential data that you're working on, etc.
Patrick Lists:
IIRC
On Mon, Nov 18, 2013 at 05:29:27PM +, Tom H wrote:
On Mon, Nov 18, 2013 at 4:41 PM, Suvayu Ali fatkasuvayu+li...@gmail.com
wrote:
On Mon, Nov 18, 2013 at 03:43:57PM +, Tom H wrote:
On Mon, Nov 18, 2013 at 3:14 PM, Suvayu Ali fatkasuvayu+li...@gmail.com
wrote:
I have been very
On Mon, Nov 18, 2013 at 07:31:21PM +0200, Joonas Sarajärvi wrote:
2013/11/18 Suvayu Ali fatkasuvayu+li...@gmail.com:
Hi Jonas,
I have a comment, and a question.
On Sun, Nov 17, 2013 at 03:46:55PM +0200, Joonas Sarajärvi wrote:
The journald log format is documented at least to some
On Mon, Nov 18, 2013 at 07:44:55PM +0200, Joonas Sarajärvi wrote:
Sorry for posting again so soon and replying to myself, but I just
noticed one very useful thing that might help quite much in the
specific problem you described:
2013/11/18 Joonas Sarajärvi m...@iki.fi:
2013/11/18 Suvayu
Steven Stern wrote:
On 11/15/2013 04:46 AM, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit,
In what way might the logs be hazardous?
It was mean mainly from administrator view. When things go bad,
machine HW/SW fail or any other
Allegedly, on or about 17 November 2013, Frantisek Hanzlik sent:
Binary logs, by contrast, may be useless when log file is damaged or I
haven't this one unique utility for reading them. And my experiences
with systems where binary logs are implemented says clearly that
binary logs is bad idea.
On 11/17/2013 11:21 AM, Tim wrote:
Allegedly, on or about 17 November 2013, Frantisek Hanzlik sent:
Binary logs, by contrast, may be useless when log file is damaged or I
haven't this one unique utility for reading them. And my experiences
with systems where binary logs are implemented says
On Sun, 17 Nov 2013 12:12:08 +0100
Patrick Lists fedora-l...@puzzled.xs4all.nl wrote:
IIRC that's the reason why journald supports encryption.
It's not encrypted it's binary,
similar to any compiled app or virus.
--
Regards,
Frank
www.frankly3d.com
--
users mailing list
On 11/17/2013 12:16 PM, Frank Murphy wrote:
On Sun, 17 Nov 2013 12:12:08 +0100
Patrick Lists fedora-l...@puzzled.xs4all.nl wrote:
IIRC that's the reason why journald supports encryption.
It's not encrypted it's binary,
similar to any compiled app or virus.
I meant the transmission of
On Sun, 17 Nov 2013 12:37:03 +0100
Patrick Lists fedora-l...@puzzled.xs4all.nl wrote:
I meant the transmission of the log to another log server. Not the
log itself. Anyway, here is Lennart Poettering's rationale behind
journald:
One of the things you will see after a hard reset is:
On Sun, Nov 17, 2013 at 12:12 PM, Patrick Lists
fedora-l...@puzzled.xs4all.nl wrote:
On 11/17/2013 11:21 AM, Tim wrote:
Allegedly, on or about 17 November 2013, Frantisek Hanzlik sent:
Binary logs, by contrast, may be useless when log file is damaged or I
haven't this one unique utility for
2013/11/17 Frantisek Hanzlik fra...@hanzlici.cz:
Steven Stern wrote:
On 11/15/2013 04:46 AM, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit,
In what way might the logs be hazardous?
It was mean mainly from administrator view. When
Joonas Sarajärvi wrote:
2013/11/17 Frantisek Hanzlik fra...@hanzlici.cz:
Steven Stern wrote:
On 11/15/2013 04:46 AM, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit,
In what way might the logs be hazardous?
It was mean mainly from
On 11/17/2013 12:32 PM, Frantisek Hanzlik wrote:
I'm convinced it is as similar things on eg. ms windows (binary logs,
registry,...) - when is all working fine, then it look fine too.
Yes. When there's a major crash, you may not have access to the fancy
programs for reading binary logs,
On Sun, Nov 17, 2013 at 12:46:40PM -0800, Joe Zeff wrote:
On 11/17/2013 12:32 PM, Frantisek Hanzlik wrote:
I'm convinced it is as similar things on eg. ms windows (binary logs,
registry,...) - when is all working fine, then it look fine too.
Yes. When there's a major crash, you may not have
On 11/17/2013 02:18 PM, Olav Vitters wrote:
A GUI for the journal is already being developed.
https://wiki.gnome.org/Apps/Logs
That's nice, although I'd like to have a CLI reader as well if there
isn't one already.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change
On Sat, Nov 16, 2013 at 10:44:21PM +0100, Frantisek Hanzlik wrote:
I agree, all systemd stuff seems very crude for me.
And 'enough time' to debug or help to fix systemd monster I really not
have, I even don't have time to report all bugs which happens to me.
Thus I must only wish to systemd
Hi
On Sun, Nov 17, 2013 at 5:39 PM, Joe Zeff wrote:
That's nice, although I'd like to have a CLI reader as well if there isn't
one already.
There is and it has been mentioned before. Use journalctl.
Rahul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change
Tim:
And if logs are in a format that you cannot read, you cannot safely
submit them to an outside server. You don't know what they contain.
Logon credentials, confidential data that you're working on, etc.
Patrick Lists:
IIRC that's the reason why journald supports encryption. I don't
Rick Stevens wrote:
On 11/15/2013 02:46 AM, Frantisek Hanzlik issued this missive:
For one thing I'm in the conviction that binary logs are hazardous
bullshit, for another on my two F19 machines systemd-journald occupy
significant part of resources (after several days it is often 1.5 to
2.5
Mateusz Marzantowicz wrote:
On 15.11.2013 11:46, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit, for another on my two F19 machines systemd-journald occupy
significant part of resources (after several days it is often 1.5 to
2.5 GB RAM and
On 11/15/2013 04:46 AM, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit,
In what way might the logs be hazardous?
--
-- Steve
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
On Sat, Nov 16, 2013 at 11:18 AM, Frantisek Hanzlik fra...@hanzlici.cz wrote:
I tried delete '/usr/lib/systemd/systemd-journald', but this may not be
called clean solution. And after that, several services (e.g. sendmail,
dovecot, sshd - what I shortly browse) stop logging via rsyslogd. On
For one thing I'm in the conviction that binary logs are hazardous
bullshit, for another on my two F19 machines systemd-journald occupy
significant part of resources (after several days it is often 1.5 to
2.5 GB RAM and several GB on /var/log/journal/*/* filesystem).
Then, how I can avoid this
On 11/15/2013 02:46 AM, Frantisek Hanzlik issued this missive:
For one thing I'm in the conviction that binary logs are hazardous
bullshit, for another on my two F19 machines systemd-journald occupy
significant part of resources (after several days it is often 1.5 to
2.5 GB RAM and several GB on
On 15.11.2013 11:46, Frantisek Hanzlik wrote:
For one thing I'm in the conviction that binary logs are hazardous
bullshit, for another on my two F19 machines systemd-journald occupy
significant part of resources (after several days it is often 1.5 to
2.5 GB RAM and several GB on
34 matches
Mail list logo
