On Tue, 09.10.12 10:45, Matthew Miller (mat...@fedoraproject.org) wrote:
i) You always see the full set of logs you have access to. No need
anymore to to look through /var/log/messages, /var/log/secure and so
on one individually. And you get all of this nicely interleaved.
As noted
On Tue, 09.10.12 11:00, Matthew Miller (mat...@fedoraproject.org) wrote:
On Tue, Oct 09, 2012 at 10:45:24AM -0400, Matthew Miller wrote:
c) it auto-pages if run on a tty
Hmmm. That's not necessarily what people are expecting, but okay.
To expand on this: there is a general expectation
On Tue, 09.10.12 11:30, Matthew Miller (mat...@fedoraproject.org) wrote:
On Tue, Oct 09, 2012 at 05:24:42PM +0200, Richard Marko wrote:
Compared to the other things I mentioned this is less important (because
hey, sysadmins can learn new ways!), but I wanted to elaborate on where
this
On 10/09/2012 05:55 AM, john.flor...@dart.biz wrote:
From: Jóhann B. Guðmundsson johan...@gmail.com
I personally want to see the documentation releng/fesco has about what
the default minimal set, what the process is to have something
include,excluded from it and why the packages that exist in
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
Only users in the adm group can see system logs and logs of
other users.
Is this configurable (if so, how)? For example, all the wheel is
special behavior I am aware of is configurable (e.g. PAM config,
visudo).
Also: what is the
On Tue, 09.10.12 13:40, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
Only users in the adm group can see system logs and logs of
other users.
Is this configurable (if so, how)? For example, all the wheel is
special behavior I am
On Tue, 9 Oct 2012, Lennart Poettering wrote:
Rotation happens in-line, i.e. each time before we are about to write an
entry we check if rotation is necessary and execute it. This should make
things a lot more robust, as this fixes a common issue with syslog where
a lot of data generated in
On Tue, Oct 09, 2012 at 03:14:06PM -0400, Seth Vidal wrote:
This must be changed. Many policies at IT departments world wide
have a date-based requirement, not a disk space size.
It is simply unacceptable.
https://bugzilla.redhat.com/show_bug.cgi?id=864629
--
Matthew Miller ☁☁☁ Fedora
Am 09.10.2012 19:19, schrieb Lennart Poettering:
On Tue, 09.10.12 15:19, Tom Hughes (t...@compton.nu) wrote:
On 09/10/12 15:04, Lennart Poettering wrote:
h) It's much shorter to type: journalctl than less
/var/log/messages. journalctl -n is shorter than tail
/var/log/messages. And
On Tue, 2012-10-09 at 21:29 +0200, Reindl Harald wrote:
Am 09.10.2012 19:19, schrieb Lennart Poettering:
On Tue, 09.10.12 15:19, Tom Hughes (t...@compton.nu) wrote:
On 09/10/12 15:04, Lennart Poettering wrote:
h) It's much shorter to type: journalctl than less
/var/log/messages.
On Tue, Oct 09, 2012 at 07:51:30PM +0200, Lennart Poettering wrote:
To summarize:
Previously: /var/log/secure readable only for root, /var/log/messages
readable for everybody and including data from everybody.
Currently (Fedora 17 and before) /var/log/message is only readably by
root.
From: Jesse Keating jkeat...@redhat.com
On 10/09/2012 05:55 AM, john.flor...@dart.biz wrote:
From: Jóhann B. Guðmundsson johan...@gmail.com
I personally want to see the documentation releng/fesco has about
what
the default minimal set, what the process is to have something
On Tue, Oct 09, 2012 at 03:55:30PM -0400, john.flor...@dart.biz wrote:
So maybe I should say that I think Fedora has always had it just about
right, IMHO. A very small, but functional system ready to grow and can do
so with its own tools.
Yeah, but there's _so much_ room to quibble over
From: Matthew Miller mat...@fedoraproject.org
On Tue, Oct 09, 2012 at 03:55:30PM -0400, john.flor...@dart.biz wrote:
So maybe I should say that I think Fedora has always had it just about
right, IMHO. A very small, but functional system ready to grow and
can do
so with its own tools.
On Tue, 2012-10-09 at 20:47 +0200, Lennart Poettering wrote:
On Tue, 09.10.12 13:40, Chris Adams (cmad...@hiwaay.net) wrote:
Once upon a time, Lennart Poettering mzerq...@0pointer.de said:
Only users in the adm group can see system logs and logs of
other users.
Is this configurable
On Oct 9, 2012, at 11:20 AM, Lennart Poettering wrote:
On Tue, 09.10.12 15:35, Bryn M. Reeves (b...@redhat.com) wrote:
Setting PIPE or piping to a pager is even worse - the lines are
truncated at 77 chars regardless of the term width so for now I'm
running journalctl --no-pager -a | less to
On Tue, 09.10.12 16:53, Simo Sorce (s...@redhat.com) wrote:
Also: what is the equivalent for logrotate in the systemd journal
case?
Rotation happens in-line, i.e. each time before we are about to write an
entry we check if rotation is necessary and execute it. This should make
On Tue, 09.10.12 14:57, Chris Murphy (li...@colorremedies.com) wrote:
On Oct 9, 2012, at 11:20 AM, Lennart Poettering wrote:
On Tue, 09.10.12 15:35, Bryn M. Reeves (b...@redhat.com) wrote:
Setting PIPE or piping to a pager is even worse - the lines are
truncated at 77 chars regardless
On Tue, Oct 09, 2012 at 11:26:19PM +0200, Lennart Poettering wrote:
Well, you have to actually enable the journal on persistent storage
first. Try mkdir /var/log/journal. Without that we will only keep a
very small set of logs in RAM, so that things are flushed out quickly.
So, minutes before
On 9 October 2012 15:24, Lennart Poettering mzerq...@0pointer.de wrote:
On Tue, 09.10.12 16:53, Simo Sorce (s...@redhat.com) wrote:
If you want audit-like semantics with crashing if we cannot write, then
use something else, not the journal. The journal is supposed to be
robust and do the
On 9 October 2012 15:50, Matthew Miller mat...@fedoraproject.org wrote:
On Tue, Oct 09, 2012 at 03:41:51PM -0600, Stephen John Smoogen wrote:
If you want audit-like semantics with crashing if we cannot write, then
use something else, not the journal. The journal is supposed to be
robust and
On Tue, 2012-10-09 at 15:41 -0600, Stephen John Smoogen wrote:
On 9 October 2012 15:24, Lennart Poettering mzerq...@0pointer.de wrote:
On Tue, 09.10.12 16:53, Simo Sorce (s...@redhat.com) wrote:
If you want audit-like semantics with crashing if we cannot write, then
use something else,
On Tue, 09.10.12 15:41, Stephen John Smoogen (smo...@gmail.com) wrote:
On 9 October 2012 15:24, Lennart Poettering mzerq...@0pointer.de wrote:
On Tue, 09.10.12 16:53, Simo Sorce (s...@redhat.com) wrote:
If you want audit-like semantics with crashing if we cannot write, then
use something
On Tue, 2012-10-09 at 15:57 -0600, Stephen John Smoogen wrote:
On 9 October 2012 15:50, Matthew Miller mat...@fedoraproject.org wrote:
On Tue, Oct 09, 2012 at 03:41:51PM -0600, Stephen John Smoogen wrote:
If you want audit-like semantics with crashing if we cannot write, then
use
On 9 October 2012 16:08, Lennart Poettering mzerq...@0pointer.de wrote:
On Tue, 09.10.12 15:41, Stephen John Smoogen (smo...@gmail.com) wrote:
On 9 October 2012 15:24, Lennart Poettering mzerq...@0pointer.de wrote:
On Tue, 09.10.12 16:53, Simo Sorce (s...@redhat.com) wrote:
If you want
On 9 October 2012 17:18, Dan Williams d...@redhat.com wrote:
On Tue, 2012-10-09 at 15:57 -0600, Stephen John Smoogen wrote:
On 9 October 2012 15:50, Matthew Miller mat...@fedoraproject.org wrote:
On Tue, Oct 09, 2012 at 03:41:51PM -0600, Stephen John Smoogen wrote:
If you want audit-like
On 9 October 2012 16:24, Matthew Miller mat...@fedoraproject.org wrote:
On Tue, Oct 09, 2012 at 04:20:14PM -0600, Stephen John Smoogen wrote:
If you have strict requirements on time-based logging rotation or
certain audit requirements, then something like rsyslog(?) is required
in parallel
On 10/09/2012 10:08 PM, Lennart Poettering wrote:
With the feature I am planning to propose for F19:
Which in essence is the same as I proposed for F18 ( Although for
completely different purposes ).
There was absolutely nothing preventing this feature having been
accepted and those
On Tue, 2012-10-09 at 23:24 +0200, Lennart Poettering wrote:
I am not generally against adding time-based rotation, but really,
this
is much less of a necessity than other things the journal provides,
which syslog does not: for example per-service rate limits, and
unfakable meta-data for log
On Tue, Oct 09, 2012 at 10:30:38PM -0400, Simo Sorce wrote:
Oh come on, stop bashing unix, logrotate could certainly grow a size
checking policy if people felt the need, unix is not holding you back,
in fact you are building this stuff on a unix-like system.
In fact, logrotate _has_ a size
On Tue, 2012-10-09 at 22:33 -0400, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 10:30:38PM -0400, Simo Sorce wrote:
Oh come on, stop bashing unix, logrotate could certainly grow a size
checking policy if people felt the need, unix is not holding you back,
in fact you are building this
On 9 October 2012 20:45, Simo Sorce s...@redhat.com wrote:
On Tue, 2012-10-09 at 22:33 -0400, Matthew Miller wrote:
On Tue, Oct 09, 2012 at 10:30:38PM -0400, Simo Sorce wrote:
Oh come on, stop bashing unix, logrotate could certainly grow a size
checking policy if people felt the need, unix
101 - 132 of 132 matches
Mail list logo
