On Wed, Jul 17, 2013 at 7:54 PM, Miloslav Trmač wrote:
> rsyslog has facilities to read from journal, send the full data in
> text, receive and read it back, and even write it back to journal at
> the destination. (Full disclosure I haven't actually tried such a
> chain up, and I wouldn't be sur
On Wed, 17.07.13 19:42, Miloslav Trmač (m...@volny.cz) wrote:
> On Tue, Jul 16, 2013 at 1:34 AM, Matthew Miller
> wrote:
> > Personally, I'd be interested in seeing a lightweight
> > forwarder which integrates with, say, Logstash.
> More lightweight than running rsyslog with local logging turned
On Wed, Jul 17, 2013 at 07:54:17PM +0200, Miloslav Trmač wrote:
> rsyslog has facilities to read from journal, send the full data in
> text, receive and read it back, and even write it back to journal at
> the destination. (Full disclosure I haven't actually tried such a
> chain up, and I wouldn't
On Wed, Jul 17, 2013 at 7:52 PM, Matthew Miller
wrote:
> On Wed, Jul 17, 2013 at 07:42:49PM +0200, Miloslav Trmač wrote:
>> > Personally, I'd be interested in seeing a lightweight
>> > forwarder which integrates with, say, Logstash.
>> More lightweight than running rsyslog with local logging turne
On Wed, Jul 17, 2013 at 07:42:49PM +0200, Miloslav Trmač wrote:
> > Personally, I'd be interested in seeing a lightweight
> > forwarder which integrates with, say, Logstash.
> More lightweight than running rsyslog with local logging turned off?
> Is the overhead of rsyslog in such a configuration r
On Tue, Jul 16, 2013 at 1:34 AM, Matthew Miller
wrote:
> Personally, I'd be interested in seeing a lightweight
> forwarder which integrates with, say, Logstash.
More lightweight than running rsyslog with local logging turned off?
Is the overhead of rsyslog in such a configuration really a concern?
On Mon, 2013-07-15 at 18:39 -0400, Matthew Miller wrote:
> I'm also pretty well sold on the idea that journald is better on the
> desktop. But that's not my thing.
I agree. I would also like to stop the double-logging on the desktop.
We're working on a graphical journal frontend now, and we will
On Mon, Jul 15, 2013 at 08:46:55PM -0500, Chris Adams wrote:
> Once upon a time, Zbigniew Jędrzejewski-Szmek said:
> > The total space taken by journal is limited by size and percantage of
> > free space on the /var/log/journal filesystem [1], and age
> > [2]. Individual journal files are limited
Once upon a time, Zbigniew Jędrzejewski-Szmek said:
> The total space taken by journal is limited by size and percantage of
> free space on the /var/log/journal filesystem [1], and age
> [2]. Individual journal files are limited by size and age [3,4].
Thanks, I see there's a journald.conf now. A
On Mon, Jul 15, 2013 at 07:27:57PM -0500, Chris Adams wrote:
> If it isn't too much of a thread-drift - this brings to mind another
> question: how are the journal files rotated, archived, etc.? I don't
> see anything in the man page.
You can also use time-based rotation policies, but it's not ve
On Mon, Jul 15, 2013 at 07:27:57PM -0500, Chris Adams wrote:
> Once upon a time, Lennart Poettering said:
> > Well, the duplicate log files will be accounted for every instance of a
> > container/VM. The more containers you run, the more often you pay for
> > it. This is different than just having
Once upon a time, Lennart Poettering said:
> Well, the duplicate log files will be accounted for every instance of a
> container/VM. The more containers you run, the more often you pay for
> it. This is different than just having one package installed too much in
> the image, which can be shared a
On Mon, 15.07.13 17:21, Stephen John Smoogen (smo...@gmail.com) wrote:
> On 15 July 2013 16:39, Matthew Miller wrote:
>
> > I'm putting this in a separate thread so it doesn't get buried in the
> > enthusiasm over the other one. :)
> >
> > Here's our dilemma (Or trilemma?) in the Fedora Cloud SI
On Mon, Jul 15, 2013 at 11:35:48PM +, "Jóhann B. Guðmundsson" wrote:
> On 07/15/2013 11:34 PM, Matthew Miller wrote:
> >journald doesn't have remote logging capabilities and it's my understanding
> >that it's a non-goal. Personally, I'd be interested in seeing a lightweight
> >forwarder which i
On 07/15/2013 11:34 PM, Matthew Miller wrote:
journald doesn't have remote logging capabilities and it's my understanding
that it's a non-goal. Personally, I'd be interested in seeing a lightweight
forwarder which integrates with, say, Logstash.
Well let's not forget and easily dismiss the jour
On Mon, Jul 15, 2013 at 05:21:02PM -0600, Stephen John Smoogen wrote:
> > 1) Double-logging is a significant waste of scarce resources
> Well I can see IO resources as being scarse but how scarse are we really
> talking? [There comes a point where cutting down the size of an image isn't
> going to
On 15 July 2013 16:39, Matthew Miller wrote:
> I'm putting this in a separate thread so it doesn't get buried in the
> enthusiasm over the other one. :)
>
> Here's our dilemma (Or trilemma?) in the Fedora Cloud SIG.
>
> 1) Double-logging is a significant waste of scarce resources
>
>
Well I can s
I'm putting this in a separate thread so it doesn't get buried in the
enthusiasm over the other one. :)
Here's our dilemma (Or trilemma?) in the Fedora Cloud SIG.
1) Double-logging is a significant waste of scarce resources
2) If we disable persistent journald (the f19 approach), we lose the
18 matches
Mail list logo
