> -Original Message-
> From: Michael Biebl [mailto:mbi...@gmail.com]
> Sent: Friday, March 11, 2011 8:04 AM
> To: Andrey Borzenkov
> Cc: Mike Kazantsev; systemd-devel@lists.freedesktop.org; Rainer
> Gerhards
> Subject: Re: [systemd-devel] systemd-logger and e
> -Original Message-
> From: Michael Biebl [mailto:mbi...@gmail.com]
> Sent: Friday, March 11, 2011 8:20 AM
> To: Rainer Gerhards
> Cc: Andrey Borzenkov; Mike Kazantsev; systemd-
> de...@lists.freedesktop.org
> Subject: Re: [systemd-devel] systemd-logger and e
> -Original Message-
> From: Michael Biebl [mailto:mbi...@gmail.com]
> Sent: Friday, March 11, 2011 8:45 AM
> To: Rainer Gerhards
> Cc: systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
>
> 2011/3/11 Rain
> -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
> -Original Message-
> From: Andrey Borzenkov [mailto:arvidj...@mail.ru]
> Sent: Friday, March 11, 2011 11:01 AM
> To: Rainer Gerhards
> Cc: Michael Biebl; Mike Kazantsev; systemd-devel@lists.freedesktop.org
> Subject: Re: [systemd-devel] systemd-logger and exte
> -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-deve
> -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-deve
> -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-deve
> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Friday, March 11, 2011 5:29 PM
> To: Rainer Gerhards
> Cc: Andrey Borzenkov; Michael Biebl; Mike Kazantsev; systemd-
> de...@lists.freedesktop.org
> Subject: Re: [systemd-deve
> -Original Message-
> From: Andrey Borzenkov [mailto:arvidj...@mail.ru]
> Sent: Friday, March 11, 2011 5:42 PM
> To: Lennart Poettering
> Cc: Michael Biebl; systemd-devel@lists.freedesktop.org; Rainer Gerhards
> Subject: Re: [systemd-devel] systemd-logger and exte
> -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-logge
> -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-logge
On 03/18/2011 01:53 PM, Kay Sievers wrote:
On Fri, Mar 18, 2011 at 08:19, Rainer Gerhards wrote:
-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
> -Original Message-
> From: Lennart Poettering [mailto:lenn...@poettering.net]
> Sent: Wednesday, April 20, 2011 2:33 AM
> To: Michael Biebl
> Cc: Mike Kazantsev; systemd-devel@lists.freedesktop.org; Rainer
> Gerhards
> Subject: Re: [systemd-devel] rsyslog drops m
Hi all,
I hope this is the right list. I wonder what systemd does if the
syslogd does not start when told to do so.
Reason behind this question: in rsyslog, I try hard to record messages
even if rsyslog.conf is screwed up. For that reason, I accept
partially complete configs. And if things go rea
On Wed, Jul 6, 2011 at 4:17 PM, Lennart Poettering
wrote:
> On Wed, 06.07.11 16:11, Rainer Gerhards (rgerha...@gmail.com) wrote:
> Yes, if rsyslog dies, then systemd will notice it. As soon as there is
> traffic on the /dev/log socket (which might be right-away) it will then
> star
Hi there,
as you probably know, I am not a big fan of the journald proposal, but
that's not the point of my question. I am thinking about how to
integrate journal data into a syslog logging solution. So I have a
couple of questions in regard to accessing the journal. The most
important one is how
On Fri, Dec 2, 2011 at 2:49 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
>> as you probably know, I am not a big fan of the journald proposal, but
>> that's not the point of my question. I am thinking about how to
>> integrate journal
On Fri, Dec 2, 2011 at 4:39 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 16:14, Rainer Gerhards wrote:
>> On Fri, Dec 2, 2011 at 2:49 PM, Kay Sievers wrote:
>>> On Fri, Dec 2, 2011 at 13:59, Rainer Gerhards wrote:
>>>> as you probably know, I am not a big fan
On Fri, Dec 2, 2011 at 6:59 PM, Kay Sievers wrote:
> On Fri, Dec 2, 2011 at 17:02, Rainer Gerhards wrote:
>> On Fri, Dec 2, 2011 at 4:39 PM, Kay Sievers wrote:
>
>>> /dev/log will be read by journald. The syslog.socket filedescriptor
>>> that the syslog daemon
On Fri, Dec 2, 2011 at 7:47 PM, Kay Sievers wrote:
>>> Well, if syslogd, or any other consumer, is interested in the
>>> metadata, it should not rely in /dev/log. /dev/log will probably stay
>>> what it is which is mostly plain old syslog with a header and a
>>> timestamp and the human readable st
On Sat, Dec 3, 2011 at 12:54 PM, Kay Sievers wrote:
> Well, that's not making it hard to access information, it's trying
> hard not to break established interfaces. If syslog *could* be
> extended in a reasonable way, we wouldn't need a journal interface at
> all. Adding any information might brea
On Sat, Dec 3, 2011 at 5:18 PM, Kay Sievers wrote:
> You can just add a tiny bridge or make rsyslog receive the proper data
> which has no fixed wire format at all, but is an API we can extend as
> needed.
>
> Honestly, I really don't understand your claims, all will be available
> to you with jus
On Sat, Dec 3, 2011 at 6:12 PM, Kay Sievers wrote:
> It's called a 'cursor', a text string that is portable even across
> machines, it will point to the closest possible record in the stream.
> In the idea it's like the git commit hash that identifies a commit, in
> the journal context it's just n
I have digested our discussion now. Two questions came up:
The first one is a bit direct and blunt, my apologies for that. But I
want to make sure I put effort into the right place. Do you see any
benefit in an interface like I described (reading and writing the
journal from the syslogd)? Or do yo
On Mon, Dec 5, 2011 at 1:40 AM, Kay Sievers wrote:
> On Sat, Dec 3, 2011 at 20:41, Rainer Gerhards wrote:
>> I have digested our discussion now. Two questions came up:
>>
>> The first one is a bit direct and blunt, my apologies for that. But I
>> want to make sure
On Wed, Jan 11, 2012 at 7:20 AM, Michael Biebl wrote:
> Am 11. Januar 2012 05:19 schrieb Lennart Poettering :
>>
>> Compatibility with classic syslog implementations is provided, via a
>> socket /run/systemd/journal/syslog, to which all messages are forwarded,
>
> Most systems setup rsyslog to use
On Wed, Jan 11, 2012 at 4:09 PM, Lennart Poettering
wrote:
> rsyslog is actually too smart for us here, and will take the socket, but
> also open /dev/log in addition to that, which we want to avoid.
>
> I think rsyslog is actually doing the right thing here, though. It's the
> smart and the right
Hi,
I am thinking on how to detect potential fake messages, claiming to be
e.g. from the audit subsystem. Let's assume
- auditd is stopped --> audit messages are put into the kernel log
- journald controls /dev/kmsg and provides these via the the journal
log socket to syslogd
- syslogd uses SCM_CR
On Sun, Mar 4, 2012 at 11:37 PM, Lennart Poettering
wrote:
> On Thu, 23.02.12 17:54, Rainer Gerhards (rgerha...@gmail.com) wrote:
>
>> Hi,
>>
>> I am thinking on how to detect potential fake messages, claiming to be
>> e.g. from the audit subsystem. Let's assu
30 matches
Mail list logo
