On 6/9/06, Gavin Maltby wrote:
> On 06/09/06 11:31, Darren Reed wrote:
> > To bring the syslogd shipped with Solaris up to a level that is
> > more in line with what is found in other systems today, I'd like
> > to propose a project to upgrade it.
> >
> > Tasks currently scoped out for this projec
Nicolas Williams wrote:
>On Fri, Jun 09, 2006 at 04:58:27PM -0400, James Carlson wrote:
>
>
>>It depends on whether there is in fact a solid problem out there that
>>this solves. I'm unconvinced on that. Giving message integrity to
>>syslog seems a bit wobbly to me, but I guess I can see why s
Nicolas Williams wrote:
>On Fri, Jun 09, 2006 at 05:53:17PM -0400, James Carlson wrote:
>
>>>Oh! Well then... But those deal in structured data also...
>>>
>>It's a bit different in that you have to specify enterpriseId in order
>>to get to a parsed message content, as opposed to just meta
>>inf
Torrey McMahon wrote:
> Darren Reed wrote:
>
>> To bring the syslogd shipped with Solaris up to a level that is
>> more in line with what is found in other systems today, I'd like
>> to propose a project to upgrade it.
>>
>> Tasks currently scoped out for this project include:
>> - introduce some
Henry B. Hotz wrote:
>
> On Jun 9, 2006, at 7:58 AM, Darren Reed wrote:
>
>> If there is any evolution of the log file format, it will
>> be to use XML. XML and structured data have featured
>> heavily in discussions about advancing syslog and the
>> benefits are clear: data gets typed. If the p
