-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Thursday, March 17, 2011 10:38 PM
To: Rainer Gerhards
Cc: Michael Biebl; Andrey Borzenkov; systemd-
de...@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
...@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
On Thu, 17.03.11 08:38, Rainer Gerhards (rgerha...@hq.adiscon.com)
wrote:
You mean a new udev/dracut/systemd on an old kernel? The messages
they
print would look a bit weird if they are used together with log msg
On Fri, Mar 18, 2011 at 14:30, Rainer Gerhards rgerha...@hq.adiscon.com wrote:
On 03/18/2011 01:53 PM, Kay Sievers wrote:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9d90c8d9cde929cbc575098e825d7c29d9f45054
That's what I understood and what I based my proposal
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Thursday, March 17, 2011 12:31 AM
To: Michael Biebl
Cc: Andrey Borzenkov; systemd-devel@lists.freedesktop.org; Rainer
Gerhards
Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
On Thu, 17.03.11 08:38, Rainer Gerhards (rgerha...@hq.adiscon.com) wrote:
You mean a new udev/dracut/systemd on an old kernel? The messages they
print would look a bit weird if they are used together with log msg
timestamping the way the kernel does it, since the kernel doesn't
recognize
On Wed, Mar 16, 2011 at 07:18, Michael Biebl mbi...@gmail.com wrote:
2011/3/16 Lennart Poettering lenn...@poettering.net:
On Sat, 12.03.11 16:31, Andrey Borzenkov (arvidj...@mail.ru) wrote:
Attached patch preserves full syslog facility marker and simply emits
it back. So userspace is free to
On Wed, 16.03.11 07:18, Michael Biebl (mbi...@gmail.com) wrote:
2011/3/16 Lennart Poettering lenn...@poettering.net:
On Sat, 12.03.11 16:31, Andrey Borzenkov (arvidj...@mail.ru) wrote:
Attached patch preserves full syslog facility marker and simply emits
it back. So userspace is
On Fri, Mar 11, 2011 at 8:35 PM, Lennart Poettering
lenn...@poettering.net wrote:
On Fri, 11.03.11 19:41, Andrey Borzenkov (arvidj...@mail.ru) wrote:
Well ... the problem really is that format is supposed to be single
printable character, which does not really support bit operations and
such.
-Original Message-
From: Andrey Borzenkov [mailto:arvidj...@mail.ru]
Sent: Friday, March 11, 2011 8:38 AM
To: Michael Biebl
Cc: Mike Kazantsev; systemd-devel@lists.freedesktop.org; Rainer
Gerhards
Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
On Fri, Mar
On Fri, 11.03.11 08:49, Mike Kazantsev (mk.frag...@gmail.com) wrote:
Hmm, that is borked. We do provider proper error levels when we write
things to kmsg. This must get lost later on. But we do strip the
facility, so that it gets replaced by kernel, that is true.
The only reason we
On Fri, 11.03.11 08:03, Michael Biebl (mbi...@gmail.com) wrote:
2011/2/26 Andrey Borzenkov arvidj...@mail.ru:
On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev mk.frag...@gmail.com
wrote:
I've recently deployed systemd on a machine that uses some syslog
monitoring software and the
On Fri, 11.03.11 08:09, Rainer Gerhards (rgerha...@hq.adiscon.com) wrote:
As you can see, when rsyslog starts up and flushes the kmsg queue, the
log messages all have the same timestamp (Mar 11 07:56:27) and they
come after the rsyslog startup message, although they were logged
before the
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Friday, March 11, 2011 5:06 PM
To: Rainer Gerhards
Cc: Michael Biebl; Andrey Borzenkov; Mike Kazantsev; systemd-
de...@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-logger and external
On Fri, 11.03.11 08:45, Michael Biebl (mbi...@gmail.com) wrote:
2011/3/11 Rainer Gerhards rgerha...@hq.adiscon.com:
So isn't that already a solution?
The problem with PRINTK_TIME afaics is that it needs to be turned on
explicitly whereas I'd expect SO_TIMESTAMP will be available
On Fri, 11.03.11 10:37, Andrey Borzenkov (arvidj...@mail.ru) wrote:
On Fri, Mar 11, 2011 at 10:03 AM, Michael Biebl mbi...@gmail.com wrote:
For me the log messages actually look slightly different, as I also
get the kernel timestamp and I also noticed a different problem:
Mar 11
On Fri, 11.03.11 09:55, Rainer Gerhards (rgerha...@hq.adiscon.com) wrote:
Sounds quite reasonable :)
What would be also really nice - some systemd specific marker so
rsyslog could extract syslogd messages from kmsg. Not sure if it is
really doable without some gross kernel hack though.
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Friday, March 11, 2011 5:17 PM
To: Rainer Gerhards
Cc: Andrey Borzenkov; Michael Biebl; Mike Kazantsev; systemd-
de...@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-logger and external
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Friday, March 11, 2011 5:22 PM
To: Rainer Gerhards
Cc: Michael Biebl; Andrey Borzenkov; Mike Kazantsev; systemd-
de...@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-logger and external
On Fri, 11.03.11 17:22, Rainer Gerhards (rgerha...@hq.adiscon.com) wrote:
Systemd shuffles the system log socket to the kernel log. That is
nice, because we have logging available right from the system start.
However, in rsyslog users can configure different rules based on the
log
On Fri, Mar 11, 2011 at 17:47, Rainer Gerhards rgerha...@hq.adiscon.com wrote:
From: Andrey Borzenkov [mailto:arvidj...@mail.ru]
Well ... the problem really is that format is supposed to be single
printable
character, which does not really support bit operations and such. What
about
On Fri, 11.03.11 19:41, Andrey Borzenkov (arvidj...@mail.ru) wrote:
Well ... the problem really is that format is supposed to be single
printable character, which does not really support bit operations and
such. What about attached (completely untested) path - which adds u
marker to anything
On Fri, 11 Mar 2011 17:01:46 +0100
Lennart Poettering lenn...@poettering.net wrote:
On Fri, 11.03.11 08:49, Mike Kazantsev (mk.frag...@gmail.com) wrote:
Hmm, that is borked. We do provider proper error levels when we write
things to kmsg. This must get lost later on. But we do strip the
On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev mk.frag...@gmail.com wrote:
How the kmsg-syslogd-rsyslog migration (for systemd output) is supposed
to work?
As I just went through all of it ...
you absolutely need rsyslog that supports passing sockets from
systemd. Otherwise it is race
On Thu, 10.03.11 23:08, Mike Kazantsev (mk.frag...@gmail.com) wrote:
On Thu, 10 Mar 2011 19:14:29 +0300
Andrey Borzenkov arvidj...@mail.ru wrote:
On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev mk.frag...@gmail.com
wrote:
How the kmsg-syslogd-rsyslog migration (for systemd output)
On Thu, 10 Mar 2011 22:01:39 +0100
Lennart Poettering lenn...@poettering.net wrote:
On Wed, 23.02.11 12:48, Mike Kazantsev (mk.frag...@gmail.com) wrote:
Good day,
I've recently deployed systemd on a machine that uses some syslog
monitoring software and the software went nuts
2011/3/11 Rainer Gerhards rgerha...@hq.adiscon.com:
-Original Message-
From: Michael Biebl [mailto:mbi...@gmail.com]
Sent: Friday, March 11, 2011 8:04 AM
Mar 11 07:56:27 pluto kernel: [ 5921.140864] michael[25078]: baz
As you can see, when rsyslog starts up and flushes the kmsg
On Fri, Mar 11, 2011 at 10:03 AM, Michael Biebl mbi...@gmail.com wrote:
For me the log messages actually look slightly different, as I also
get the kernel timestamp and I also noticed a different problem:
Mar 11 07:56:27 pluto kernel: imklog 5.7.8, log source = /proc/kmsg started.
Mar 11
On Wed, Feb 23, 2011 at 10:48 AM, Mike Kazantsev mk.frag...@gmail.com wrote:
Good day,
I've recently deployed systemd on a machine that uses some syslog
monitoring software and the software went nuts because messages from
systemd logger were inconsistent with other logging - they all look
28 matches
Mail list logo
