On Fri, Jul 12, 2013 at 1:08 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Wed, 10.07.13 12:30, Umut Tezduyar (u...@tezduyar.com) wrote:
We though about just bumping this globally via sysctl, but we feared
that might not sit well with some folks, as we shouldn't change a global
On Wed, 10.07.13 12:30, Umut Tezduyar (u...@tezduyar.com) wrote:
We though about just bumping this globally via sysctl, but we feared
that might not sit well with some folks, as we shouldn't change a global
setting just because one user of it would benefit, especially given that
we don't
On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
lenn...@poettering.net wrote:
On Sun, 07.07.13 19:18, Umut Tezduyar (u...@tezduyar.com) wrote:
Hi,
I have noticed that if journal fails to send messages to
/run/systemd/journal/syslog, it increments a counter and every 30
seconds it prints
On Wed, Jul 10, 2013 at 12:30 PM, Umut Tezduyar u...@tezduyar.com wrote:
On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
lenn...@poettering.net wrote:
We though about just bumping this globally via sysctl, but we feared
that might not sit well with some folks, as we shouldn't change a
On Wed, Jul 10, 2013 at 12:55 PM, Kay Sievers k...@vrfy.org wrote:
On Wed, Jul 10, 2013 at 12:30 PM, Umut Tezduyar u...@tezduyar.com wrote:
On Tue, Jul 9, 2013 at 1:58 AM, Lennart Poettering
lenn...@poettering.net wrote:
We though about just bumping this globally via sysctl, but we feared
On Sun, 07.07.13 19:18, Umut Tezduyar (u...@tezduyar.com) wrote:
Hi,
I have noticed that if journal fails to send messages to
/run/systemd/journal/syslog, it increments a counter and every 30
seconds it prints out a message on journal informing that forwarding x
many messages has failed.
