Op 9 mrt. 2012, om 00:37 heeft David Lambert het volgende geschreven:
On 03/08/2012 03:07 PM, Warpme wrote:
I haven't set any limits in journal.conf - so maybe I should set them.
Unfortunately there is no man for this file (or I miss something) - so I
prefer to first understand it then
Am 9. März 2012 09:46 schrieb Koen Kooi k...@dominion.thruhere.net:
Op 9 mrt. 2012, om 00:37 heeft David Lambert het volgende geschreven:
On 03/08/2012 03:07 PM, Warpme wrote:
I haven't set any limits in journal.conf - so maybe I should set them.
Unfortunately there is no man for this file
Op 9 mrt. 2012, om 10:15 heeft Michael Biebl het volgende geschreven:
Am 9. März 2012 09:46 schrieb Koen Kooi k...@dominion.thruhere.net:
Op 9 mrt. 2012, om 00:37 heeft David Lambert het volgende geschreven:
On 03/08/2012 03:07 PM, Warpme wrote:
I haven't set any limits in journal.conf
'Twas brillig, and Lennart Poettering at 05/03/12 18:12 did gyre and gimble:
On Mon, 20.02.12 01:27, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Hi,
Not sure if this is an intended regression or not but a user reported a
problem to me recently which I thought was a little strange. It's
On 03/09/2012 02:46 AM, Koen Kooi wrote:
I can confirm the large filesizes, even with xz compression enabled. What's the
best way to debug this?
regards,
Koen
I first noticed this with a service that was Python program I was
developing. It was continually crashing and restarting itself, thus
Hi!
I was trying out the journal and the journalctl utility sometimes
crashed on me. After some debugging, I tracked it down to the fact
that next_with_matches() holds the c object pointer through the
journal_file_next_entry_for_data() call -- which apparently may re-map
the journal file,
