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 I put effort into the right plac
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 I put effort into the right place. Do you see any
> benefit in an interface like I describ
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 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
On Sat, Dec 3, 2011 at 17:36, Rainer Gerhards wrote:
> On Sat, Dec 3, 2011 at 5:18 PM, Kay Sievers wrote:
> One more question on the integration part. We now know that rsyslog
> needs to read the journal and convert that into proper syslog format.
> Given my experience with the Windows Event Log
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 15:23, Rainer Gerhards wrote:
> 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 jo
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 Fri, Dec 2, 2011 at 21:21, Rainer Gerhards wrote:
> 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
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 Fri, Dec 2, 2011 at 19:07, Rainer Gerhards wrote:
> On Fri, Dec 2, 2011 at 6:59 PM, Kay Sievers wrote:
>> On Fri, Dec 2, 2011 at 17:02, Rainer Gerhards wrote:
>> Well, if syslogd, or any other consumer, is interested in the
>> metadata, it should not rely in /dev/log. /dev/log will probably
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 receives, will be provided by journ
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 receives, will be provided by journald and have
>> all the messages which are received by /de
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 of the journald proposal, but
>>
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 of the journald proposal, but
>>> that's not the point of my question. I am thinking abou
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 data into a syslog logging so
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 data into a syslog logging solution.
You know that the syslog daemon will still see e
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
18 matches
Mail list logo
