From theinric at redhat.com  Wed Nov 14 17:59:13 2007
From: theinric at redhat.com (theinric at redhat.com)
Date: Wed, 14 Nov 2007 17:59:13 +0100
Subject: [rsyslog] gss-api support for rsyslog
Message-ID: <473B2961.9010705@redhat.com>

Hi,

here is a patch that enables rsyslog to use gss-api for authentication 
and encryption.
It adds a new commandline option '-g<port>' to listen for a connection 
wrapped with gss-api and few new configuration directives:
for server:
   $gsslistenservicename <service name>
for client:
   $gssforwardservicename <service name>
   $gssmode <encryption|integrity|none>

With gssmode set to "encryption" or "integrity" all tcp selectors will 
be forwarding messages via gss-api.

http://people.redhat.com/pvrabec/rpms/rsyslog/rsyslog-1.19.10-gssapi.patch

Comments are welcome.

From mbiebl at gmail.com  Wed Nov 14 18:50:17 2007
From: mbiebl at gmail.com (Michael Biebl)
Date: Wed, 14 Nov 2007 18:50:17 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <473B2961.9010705@redhat.com>
References: <473B2961.9010705@redhat.com>
Message-ID: <aa76cdac0711140950u5f5243b7kd7cb83671b9c79de@mail.gmail.com>

2007/11/14, theinric at redhat.com <theinric at redhat.com>:
> Hi,
>
> here is a patch that enables rsyslog to use gss-api for authentication
> and encryption.
> It adds a new commandline option '-g<port>' to listen for a connection
> wrapped with gss-api and few new configuration directives:
> for server:
>    $gsslistenservicename <service name>
> for client:
>    $gssforwardservicename <service name>
>    $gssmode <encryption|integrity|none>
>
> With gssmode set to "encryption" or "integrity" all tcp selectors will
> be forwarding messages via gss-api.

Nice work! The only thing missing imho is documentation:
rsyslogd --help does not list the paramenter, man rsyslogd also.
man rsyslog.conf should document the new configuration directives and
a html file in doc/ would be nice too.

Cheers,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

From theinric at redhat.com  Thu Nov 15 11:01:25 2007
From: theinric at redhat.com (theinric at redhat.com)
Date: Thu, 15 Nov 2007 11:01:25 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <aa76cdac0711140950u5f5243b7kd7cb83671b9c79de@mail.gmail.com>
References: <473B2961.9010705@redhat.com>
	<aa76cdac0711140950u5f5243b7kd7cb83671b9c79de@mail.gmail.com>
Message-ID: <473C18F5.4000806@redhat.com>

On 11/14/2007 06:50 PM, Michael Biebl wrote:
> 2007/11/14, theinric at redhat.com <theinric at redhat.com>:
>> Hi,
>>
>> here is a patch that enables rsyslog to use gss-api for authentication
>> and encryption.
>> It adds a new commandline option '-g<port>' to listen for a connection
>> wrapped with gss-api and few new configuration directives:
>> for server:
>>    $gsslistenservicename <service name>
>> for client:
>>    $gssforwardservicename <service name>
>>    $gssmode <encryption|integrity|none>
>>
>> With gssmode set to "encryption" or "integrity" all tcp selectors will
>> be forwarding messages via gss-api.
> 
> Nice work! The only thing missing imho is documentation:
> rsyslogd --help does not list the paramenter, man rsyslogd also.
> man rsyslog.conf should document the new configuration directives and
> a html file in doc/ would be nice too.

You're right, documentation hasn't been added yet. I want to wait for 
more feedback and maybe someone will come up with better directives 
names. :)

From rgerhards at hq.adiscon.com  Thu Nov 15 11:02:58 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Thu, 15 Nov 2007 11:02:58 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <473C18F5.4000806@redhat.com>
References: <473B2961.9010705@redhat.com><aa76cdac0711140950u5f5243b7kd7cb83671b9c79de@mail.gmail.com>
	<473C18F5.4000806@redhat.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308424@grfint2.intern.adiscon.com>

In any case, it's a real nice piece of work. I have just returned from
the US (this Monday) and there is still a pile of work I need to look
at. I think next Monday I'll go back to rsyslog and integrating that
patch is probably the #1 thing to do ;)

Thanks,
Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of theinric at redhat.com
> Sent: Thursday, November 15, 2007 11:01 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] gss-api support for rsyslog
> 
> On 11/14/2007 06:50 PM, Michael Biebl wrote:
> > 2007/11/14, theinric at redhat.com <theinric at redhat.com>:
> >> Hi,
> >>
> >> here is a patch that enables rsyslog to use gss-api for
> authentication
> >> and encryption.
> >> It adds a new commandline option '-g<port>' to listen for a
> connection
> >> wrapped with gss-api and few new configuration directives:
> >> for server:
> >>    $gsslistenservicename <service name>
> >> for client:
> >>    $gssforwardservicename <service name>
> >>    $gssmode <encryption|integrity|none>
> >>
> >> With gssmode set to "encryption" or "integrity" all tcp selectors
> will
> >> be forwarding messages via gss-api.
> >
> > Nice work! The only thing missing imho is documentation:
> > rsyslogd --help does not list the paramenter, man rsyslogd also.
> > man rsyslog.conf should document the new configuration directives
and
> > a html file in doc/ would be nice too.
> 
> You're right, documentation hasn't been added yet. I want to wait for
> more feedback and maybe someone will come up with better directives
> names. :)
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From pvrabec at redhat.com  Thu Nov 15 11:12:34 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Thu, 15 Nov 2007 11:12:34 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA308424@grfint2.intern.adiscon.com>
References: <473B2961.9010705@redhat.com> <473C18F5.4000806@redhat.com>
	<577465F99B41C842AAFBE9ED71E70ABA308424@grfint2.intern.adiscon.com>
Message-ID: <200711151112.34201.pvrabec@redhat.com>

thnx. Rainer,

this is very important functionality for us. If you need any help or you have 
some questions drop us email.

btw. F8 is out for a week and there are no bug reports on rsyslog, I hope it 
will continue this way ;-)

peace :-)

On Thursday 15 November 2007 11:02:58 am Rainer Gerhards wrote:
> In any case, it's a real nice piece of work. I have just returned from
> the US (this Monday) and there is still a pile of work I need to look
> at. I think next Monday I'll go back to rsyslog and integrating that
> patch is probably the #1 thing to do ;)

From rgerhards at hq.adiscon.com  Mon Nov 19 11:08:35 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Mon, 19 Nov 2007 11:08:35 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <200711151112.34201.pvrabec@redhat.com>
References: <473B2961.9010705@redhat.com> <473C18F5.4000806@redhat.com>
	<577465F99B41C842AAFBE9ED71E70ABA308424@grfint2.intern.adiscon.com>
	<200711151112.34201.pvrabec@redhat.com>
Message-ID: <1195466915.16341.14.camel@localhost.localdomain>

Hi all,

I have just done a rough review of the patch. From the code point of
view it looks very well. So I have committed it to CVS, its now
available.

However, I am not yet 100% sure on how it is used. Maybe you can give me
a jump start with a few notes on how to set it up and what to expect.
That would enable me to better follow the code. And, yes, I know its all
there in the code... ;)

Thanks again for your great help. This indeed looks like a very
important addition to rsyslog.

Rainer


On Thu, 2007-11-15 at 11:12 +0100, Peter Vrabec wrote:
> thnx. Rainer,
> 
> this is very important functionality for us. If you need any help or you have 
> some questions drop us email.
> 
> btw. F8 is out for a week and there are no bug reports on rsyslog, I hope it 
> will continue this way ;-)
> 
> peace :-)
> 
> On Thursday 15 November 2007 11:02:58 am Rainer Gerhards wrote:
> > In any case, it's a real nice piece of work. I have just returned from
> > the US (this Monday) and there is still a pile of work I need to look
> > at. I think next Monday I'll go back to rsyslog and integrating that
> > patch is probably the #1 thing to do ;)
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog


From rgerhards at hq.adiscon.com  Mon Nov 19 15:29:29 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Mon, 19 Nov 2007 15:29:29 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <1195466915.16341.14.camel@localhost.localdomain>
References: <473B2961.9010705@redhat.com>
	<473C18F5.4000806@redhat.com><577465F99B41C842AAFBE9ED71E70ABA308424@grfint2.intern.adiscon.com><200711151112.34201.pvrabec@redhat.com>
	<1195466915.16341.14.camel@localhost.localdomain>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308482@grfint2.intern.adiscon.com>

I have uploaded an interim version of the applied-patch-to-version to

http://download.rsyslog.com/rsyslog/rsyslog-1.19.11.tar.gz

in case that somebody would like to have an early look at the package.
It still lacks any doc. 

Feedback is appreciated.

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Rainer Gerhards
> Sent: Monday, November 19, 2007 11:09 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] gss-api support for rsyslog
> 
> Hi all,
> 
> I have just done a rough review of the patch. From the code point of
> view it looks very well. So I have committed it to CVS, its now
> available.
> 
> However, I am not yet 100% sure on how it is used. Maybe you can give
> me
> a jump start with a few notes on how to set it up and what to expect.
> That would enable me to better follow the code. And, yes, I know its
> all
> there in the code... ;)
> 
> Thanks again for your great help. This indeed looks like a very
> important addition to rsyslog.
> 
> Rainer
> 
> 
> On Thu, 2007-11-15 at 11:12 +0100, Peter Vrabec wrote:
> > thnx. Rainer,
> >
> > this is very important functionality for us. If you need any help or
> you have
> > some questions drop us email.
> >
> > btw. F8 is out for a week and there are no bug reports on rsyslog, I
> hope it
> > will continue this way ;-)
> >
> > peace :-)
> >
> > On Thursday 15 November 2007 11:02:58 am Rainer Gerhards wrote:
> > > In any case, it's a real nice piece of work. I have just returned
> from
> > > the US (this Monday) and there is still a pile of work I need to
> look
> > > at. I think next Monday I'll go back to rsyslog and integrating
> that
> > > patch is probably the #1 thing to do ;)
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> 
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From pvrabec at redhat.com  Tue Nov 20 16:09:17 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Tue, 20 Nov 2007 16:09:17 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA308482@grfint2.intern.adiscon.com>
References: <473B2961.9010705@redhat.com>
	<1195466915.16341.14.camel@localhost.localdomain>
	<577465F99B41C842AAFBE9ED71E70ABA308482@grfint2.intern.adiscon.com>
Message-ID: <200711201609.18602.pvrabec@redhat.com>

in case you need some help setting up krb stuff, here is some info:

http://web.mit.edu/kerberos/www/krb5-1.6/
http://cryptnet.net/fdp/admin/kerby-infra/en/kerby-infra.html#install

how was our env. set up? just brief instructions:

SERVER SIDE (xen41.englab.brq.redhat.com)  in WRABCO.ORG realm
- running KDC, rsyslog listen to gss connections
- 2 principals were added  to database:
host/xen41.englab.brq.redhat.com at WRABCO.ORG
pvrabec at WRABCO.ORG
- host/xen41.englab.brq.redhat.com at WRABCO.ORG must be exported to keytab 
file /etc/krb5.keytab
- rsyslog started with -g514 option (not -t option is used)

CLIENT SIDE
- get ticket from kdc (#kinit pvrabec)
- configure rsyslog (/etc/rsyslog.conf)
$gssmode encryption
*.info;mail.none;authpriv.none;cron.none                @@xen41
- start rsyslog
- #logger foo


On Monday 19 November 2007 03:29:29 pm Rainer Gerhards wrote:
> I have uploaded an interim version of the applied-patch-to-version to
>
> http://download.rsyslog.com/rsyslog/rsyslog-1.19.11.tar.gz
>
> in case that somebody would like to have an early look at the package.
> It still lacks any doc.
>
> Feedback is appreciated.
>
> Rainer

From rgerhards at hq.adiscon.com  Tue Nov 20 16:53:24 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Tue, 20 Nov 2007 16:53:24 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <200711201609.18602.pvrabec@redhat.com>
References: <473B2961.9010705@redhat.com><1195466915.16341.14.camel@localhost.localdomain><577465F99B41C842AAFBE9ED71E70ABA308482@grfint2.intern.adiscon.com>
	<200711201609.18602.pvrabec@redhat.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA30848B@grfint2.intern.adiscon.com>

Hi Peter,

this, as well as the doc, is most helpful. Now that we actually have doc
(I thought I'd have to pen it down ;)), I think I will release very
shortly, most probably tomorrow.

I have thought about setting up a full lab before carrying on. For now,
I have decided to NOT do that. I am sure that you folks have tested it
quite good and the code that I have seen looks excellent.

So I will pull it in as is and wait for some feedback from the field
(with the assumption "no feedback" equals "OK").

I will then begin to look at the loadable module de-initialization. This
is not really clean in the current release, but that's no problem
because modules never get unloaded. However, in the long term we need
this to be clean.

The mysterios segfault issue is still dangling. I was hesitant to do any
larger-scale new development without fixing it. But given the fact that
it is extremely hard to find, and obviously happens very seldom, I'll
continue developing. I am right now looking into upgrading the dev
machine to an x64 OS, where most of the problems happened. My hope is
that I will see a segfault during further development work and then
hopefully be able to tackle it. I still think that the segfault must be
well understood and fixed before I go into some serious multithreading
redesign. As such, unfortunately, this issue still holds some of the
work scheduled for the next *major* version.

I thought I give you an update here in my end (will also post this to
the blog for the others). Any feedback/suggestion is highly welcome.

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Peter Vrabec
> Sent: Tuesday, November 20, 2007 4:09 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] gss-api support for rsyslog
> 
> in case you need some help setting up krb stuff, here is some info:
> 
> http://web.mit.edu/kerberos/www/krb5-1.6/
> http://cryptnet.net/fdp/admin/kerby-infra/en/kerby-infra.html#install
> 
> how was our env. set up? just brief instructions:
> 
> SERVER SIDE (xen41.englab.brq.redhat.com)  in WRABCO.ORG realm
> - running KDC, rsyslog listen to gss connections
> - 2 principals were added  to database:
> host/xen41.englab.brq.redhat.com at WRABCO.ORG
> pvrabec at WRABCO.ORG
> - host/xen41.englab.brq.redhat.com at WRABCO.ORG must be exported to
> keytab
> file /etc/krb5.keytab
> - rsyslog started with -g514 option (not -t option is used)
> 
> CLIENT SIDE
> - get ticket from kdc (#kinit pvrabec)
> - configure rsyslog (/etc/rsyslog.conf)
> $gssmode encryption
> *.info;mail.none;authpriv.none;cron.none                @@xen41
> - start rsyslog
> - #logger foo
> 
> 
> On Monday 19 November 2007 03:29:29 pm Rainer Gerhards wrote:
> > I have uploaded an interim version of the applied-patch-to-version
to
> >
> > http://download.rsyslog.com/rsyslog/rsyslog-1.19.11.tar.gz
> >
> > in case that somebody would like to have an early look at the
> package.
> > It still lacks any doc.
> >
> > Feedback is appreciated.
> >
> > Rainer
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From pvrabec at redhat.com  Tue Nov 20 17:18:11 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Tue, 20 Nov 2007 17:18:11 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA30848B@grfint2.intern.adiscon.com>
References: <473B2961.9010705@redhat.com>
	<200711201609.18602.pvrabec@redhat.com>
	<577465F99B41C842AAFBE9ED71E70ABA30848B@grfint2.intern.adiscon.com>
Message-ID: <200711201718.12135.pvrabec@redhat.com>

On Tuesday 20 November 2007 04:53:24 pm Rainer Gerhards wrote:
> Hi Peter,
>
> this, as well as the doc, is most helpful. Now that we actually have doc
> (I thought I'd have to pen it down ;)), I think I will release very
> shortly, most probably tomorrow.
doc would  be perfect :-) I'm sorry I didn't have time to do it.

> I have thought about setting up a full lab before carrying on. For now,
> I have decided to NOT do that. I am sure that you folks have tested it
> quite good and the code that I have seen looks excellent.
>
> So I will pull it in as is and wait for some feedback from the field
> (with the assumption "no feedback" equals "OK").
hold on, please. There is still some development and we need to make clear in 
one thing. Here it is:
"-g" accepts only gss connections
"-t" accepts all connections (gss as a plain text)
but, we have a requirement to log both(gss and non-gss). 
Solutions:
1.  -g somePort -t someOtherPort
- this might be easy implemented

2. check if the mesaage is gss or not
- a bit hackish, since there is no protocol

I think patch is OK to release, but I'd like to avoid breaking compatibility 
in the future.

> I will then begin to look at the loadable module de-initialization. This
> is not really clean in the current release, but that's no problem
> because modules never get unloaded. However, in the long term we need
> this to be clean.
>
> The mysterios segfault issue is still dangling. I was hesitant to do any
> larger-scale new development without fixing it. But given the fact that
> it is extremely hard to find, and obviously happens very seldom, I'll
> continue developing. I am right now looking into upgrading the dev
> machine to an x64 OS, where most of the problems happened. My hope is
> that I will see a segfault during further development work and then
> hopefully be able to tackle it. I still think that the segfault must be
> well understood and fixed before I go into some serious multithreading
> redesign. As such, unfortunately, this issue still holds some of the
> work scheduled for the next *major* version.

This bug is my nightmare.  I really don't know what to do. I run 2 syslogs in 
valgrind during a weekend. Sendind message via UDP on 64 architecture, 
messages generated every 1/3sec. RESULT: no segfault. :-(

F8 is out for 2 weeks, we have only one bug report. I released an update to 
1.19.10.

> I thought I give you an update here in my end (will also post this to
> the blog for the others). Any feedback/suggestion is highly welcome.
>
> Rainer
>
> > -----Original Message-----
> > From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> > bounces at lists.adiscon.com] On Behalf Of Peter Vrabec
> > Sent: Tuesday, November 20, 2007 4:09 PM
> > To: rsyslog-users
> > Subject: Re: [rsyslog] gss-api support for rsyslog
> >
> > in case you need some help setting up krb stuff, here is some info:
> >
> > http://web.mit.edu/kerberos/www/krb5-1.6/
> > http://cryptnet.net/fdp/admin/kerby-infra/en/kerby-infra.html#install
> >
> > how was our env. set up? just brief instructions:
> >
> > SERVER SIDE (xen41.englab.brq.redhat.com)  in WRABCO.ORG realm
> > - running KDC, rsyslog listen to gss connections
> > - 2 principals were added  to database:
> > host/xen41.englab.brq.redhat.com at WRABCO.ORG
> > pvrabec at WRABCO.ORG
> > - host/xen41.englab.brq.redhat.com at WRABCO.ORG must be exported to
> > keytab
> > file /etc/krb5.keytab
> > - rsyslog started with -g514 option (not -t option is used)
> >
> > CLIENT SIDE
> > - get ticket from kdc (#kinit pvrabec)
> > - configure rsyslog (/etc/rsyslog.conf)
> > $gssmode encryption
> > *.info;mail.none;authpriv.none;cron.none                @@xen41
> > - start rsyslog
> > - #logger foo
> >
> > On Monday 19 November 2007 03:29:29 pm Rainer Gerhards wrote:
> > > I have uploaded an interim version of the applied-patch-to-version
>
> to
>
> > > http://download.rsyslog.com/rsyslog/rsyslog-1.19.11.tar.gz
> > >
> > > in case that somebody would like to have an early look at the
> >
> > package.
> >
> > > It still lacks any doc.
> > >
> > > Feedback is appreciated.
> > >
> > > Rainer
> >
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
>
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog



From rgerhards at hq.adiscon.com  Tue Nov 20 17:21:49 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Tue, 20 Nov 2007 17:21:49 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <200711201718.12135.pvrabec@redhat.com>
References: <473B2961.9010705@redhat.com><200711201609.18602.pvrabec@redhat.com><577465F99B41C842AAFBE9ED71E70ABA30848B@grfint2.intern.adiscon.com>
	<200711201718.12135.pvrabec@redhat.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA30848C@grfint2.intern.adiscon.com>

> > So I will pull it in as is and wait for some feedback from the field
> > (with the assumption "no feedback" equals "OK").
> hold on, please. There is still some development and we need to make
> clear in
> one thing. Here it is:
> "-g" accepts only gss connections
> "-t" accepts all connections (gss as a plain text)
> but, we have a requirement to log both(gss and non-gss).
> Solutions:
> 1.  -g somePort -t someOtherPort
> - this might be easy implemented
> 
> 2. check if the mesaage is gss or not
> - a bit hackish, since there is no protocol
> 
> I think patch is OK to release, but I'd like to avoid breaking
> compatibility
> in the future.

OK, valid point. Will hold, a few days don't matter, upward
compatibility is more important.

> > I will then begin to look at the loadable module de-initialization.
> This
> > is not really clean in the current release, but that's no problem
> > because modules never get unloaded. However, in the long term we
need
> > this to be clean.
> >
> > The mysterios segfault issue is still dangling. I was hesitant to do
> any
> > larger-scale new development without fixing it. But given the fact
> that
> > it is extremely hard to find, and obviously happens very seldom,
I'll
> > continue developing. I am right now looking into upgrading the dev
> > machine to an x64 OS, where most of the problems happened. My hope
is
> > that I will see a segfault during further development work and then
> > hopefully be able to tackle it. I still think that the segfault must
> be
> > well understood and fixed before I go into some serious
> multithreading
> > redesign. As such, unfortunately, this issue still holds some of the
> > work scheduled for the next *major* version.
> 
> This bug is my nightmare.  I really don't know what to do. I run 2
> syslogs in
> valgrind during a weekend. Sendind message via UDP on 64 architecture,
> messages generated every 1/3sec. RESULT: no segfault. :-(
> 
> F8 is out for 2 weeks, we have only one bug report. I released an
> update to
> 1.19.10.

My nightmare, too. I have hunted a number of bugs, but this one is
really the nastiest I have seen in over 20 years :(. You don't see it in
lab, and you don't see it in code review. And the worst thing is that I
have no clue left what may be the issue - besides that it is related to
threading. But the threading model is that simple...

Rainer

From janfrode at tanso.net  Wed Nov 21 09:53:20 2007
From: janfrode at tanso.net (Jan-Frode Myklebust)
Date: Wed, 21 Nov 2007 09:53:20 +0100
Subject: [rsyslog] gss-api support for rsyslog
References: <473B2961.9010705@redhat.com>
	<200711201609.18602.pvrabec@redhat.com>
	<577465F99B41C842AAFBE9ED71E70ABA30848B@grfint2.intern.adiscon.com>
	<200711201718.12135.pvrabec@redhat.com>
Message-ID: <slrnfk7sg0.220.janfrode@lc4eb8045376502.ibm.com>

On 2007-11-20, Peter Vrabec <pvrabec at redhat.com> wrote:
>
> This bug is my nightmare.  I really don't know what to do. I run 2 syslogs in 
> valgrind during a weekend. Sendind message via UDP on 64 architecture, 
> messages generated every 1/3sec. RESULT: no segfault. :-(

I'd just like to again point out that we're seeing this regularly
on *32-bit* RHEL5. It's a quite heavily loaded server (1-2 GB udp-syslogs a
day), and it's been failing at these times:

	Mon Sep  3 01:25:05 2007
	Mon Sep  3 15:54:19 2007
	Tue Sep  4 23:16:05 2007
	Thu Sep  6 20:38:05 2007
	Fri Sep  7 03:27:19 2007
	Sat Sep  8 06:42:34 2007
	Mon Sep 10 21:57:35 2007
	Thu Sep 13 11:06:49 2007
	Fri Sep 14 08:59:50 2007
	Fri Sep 14 14:41:04 2007
	Sat Sep 15 14:17:05 2007
	Sun Sep 16 09:10:49 2007
	Sun Sep 16 15:43:34 2007
	Mon Sep 17 22:00:04 2007
	Thu Sep 20 17:43:19 2007
	Fri Sep 21 17:27:49 2007
	Sun Sep 23 05:32:49 2007
	Sun Sep 23 15:18:49 2007
	Mon Sep 24 11:37:49 2007
	Mon Sep 24 12:31:04 2007
	Mon Sep 24 23:29:19 2007
	# upgraded to rsyslog-1.19.8-1, running with MALLOC_CHECK_=2
	Thu Sep 27 14:18:48 2007
	Fri Sep 28 21:10:17 2007
	Fri Oct  5 06:54:02 2007
	Fri Oct 26 14:26:08 2007
	Sun Nov  4 08:55:22 2007
	Wed Nov  7 17:15:52 2007
	Sat Nov 10 03:09:38 2007
	Sat Nov 10 20:07:07 2007
	
So, with 1.19.8-1 it's gotten quite a bit better for us. 
Unfortunately I haven't been able to get any core dumps,
even with DAEMON_COREFILE_LIMIT='unlimited' in 
/etc/sysconfig/rsyslog and doing a "cd /var/log/syslog" 
before starting rsyslogd in the init-script. Is there
anything else we need to do to get coredumps ?


  -jf


From pvrabec at redhat.com  Wed Nov 21 14:32:21 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Wed, 21 Nov 2007 14:32:21 +0100
Subject: [rsyslog] gss-api support for rsyslog
In-Reply-To: <slrnfk7sg0.220.janfrode@lc4eb8045376502.ibm.com>
References: <473B2961.9010705@redhat.com>
	<200711201718.12135.pvrabec@redhat.com>
	<slrnfk7sg0.220.janfrode@lc4eb8045376502.ibm.com>
Message-ID: <200711211432.21492.pvrabec@redhat.com>

Hi Jan,

thnx. for info. Could you try latest release, please.
You can get src.rpm from fedora mirrors:
ftp://mirror.colorado.edu/pub/fedora/linux/updates/8/SRPMS/rsyslog-1.19.10-1.fc8.src.rpm

Could you send your /proc/cpuinfo?

Do you use network logging? 

We try our best to reproduce the problem.

On Wednesday 21 November 2007 09:53:20 am Jan-Frode Myklebust wrote:
> On 2007-11-20, Peter Vrabec <pvrabec at redhat.com> wrote:
> > This bug is my nightmare.  I really don't know what to do. I run 2
> > syslogs in valgrind during a weekend. Sendind message via UDP on 64
> > architecture, messages generated every 1/3sec. RESULT: no segfault. :-(
>
> I'd just like to again point out that we're seeing this regularly
> on *32-bit* RHEL5. It's a quite heavily loaded server (1-2 GB udp-syslogs a
> day), and it's been failing at these times:


>
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog



From pvrabec at redhat.com  Thu Nov 22 13:59:08 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Thu, 22 Nov 2007 13:59:08 +0100
Subject: [rsyslog] rsyslog-example.conf
Message-ID: <200711221359.08874.pvrabec@redhat.com>

Hi,

would it be possible to provide some example rsyslog.conf file and install it 
with doc/*html?

http://people.redhat.com/pvrabec/rpms/rsyslog/rsyslog-example.conf

Also, note about it in rsyslog.conf.5 would be OK.

Your opinions? 


From rgerhards at hq.adiscon.com  Thu Nov 22 14:19:07 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Thu, 22 Nov 2007 14:19:07 +0100
Subject: [rsyslog] rsyslog-example.conf
In-Reply-To: <200711221359.08874.pvrabec@redhat.com>
References: <200711221359.08874.pvrabec@redhat.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA3084B7@grfint2.intern.adiscon.com>

Nice sample :). I'll add it to the next release.

BTW: I am thinking about releasing a new version with the GSS-API
version as is, BUT with a warning that it should not yet be used for
production, due to not-yet-solved compatibility issues. Any hard
objections?

Rainer
PS: I need to attend a meeting, will probably not be online until much
later or tomorrow morning...

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Peter Vrabec
> Sent: Thursday, November 22, 2007 1:59 PM
> To: rsyslog-users
> Subject: [rsyslog] rsyslog-example.conf
> 
> Hi,
> 
> would it be possible to provide some example rsyslog.conf file and
> install it
> with doc/*html?
> 
> http://people.redhat.com/pvrabec/rpms/rsyslog/rsyslog-example.conf
> 
> Also, note about it in rsyslog.conf.5 would be OK.
> 
> Your opinions?
> 
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From pvrabec at redhat.com  Thu Nov 22 14:30:06 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Thu, 22 Nov 2007 14:30:06 +0100
Subject: [rsyslog] rsyslog-example.conf
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA3084B7@grfint2.intern.adiscon.com>
References: <200711221359.08874.pvrabec@redhat.com>
	<577465F99B41C842AAFBE9ED71E70ABA3084B7@grfint2.intern.adiscon.com>
Message-ID: <200711221430.06511.pvrabec@redhat.com>

On Thursday 22 November 2007 02:19:07 pm Rainer Gerhards wrote:
> Nice sample :). I'll add it to the next release.
>
> BTW: I am thinking about releasing a new version with the GSS-API
> version as is, BUT with a warning that it should not yet be used for
> production, due to not-yet-solved compatibility issues. Any hard
> objections?
I won't push it at the moment. "-g" option will behave differently in the 
future, therefore I prefer to wait till  theinric implement it.

From rgerhards at hq.adiscon.com  Tue Nov 27 10:54:56 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Tue, 27 Nov 2007 10:54:56 +0100
Subject: [rsyslog] Looking for bughunters...
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com>

Hi all,

we are still working to hunt down the unfortunate and extremely
hard-to-find (to say the least...) segfault issue that some experience.
Peter Vrabec has created a great new RPM with debugging support. We
would appreciate if those of you experiencing the problem could give it
a try.

Full information can be found on the rsyslog site at

http://www.rsyslog.com/Article139.phtml

Your help is deeply appreciated!

Thanks,
Rainer

PS: as a reminder, I do more in-depth reports of what is happening in my
blog at http://rgerhards.blogspot.com - you may be interested to follow
it. I do this so that I do not pollute the mailing list with
too-in-depth information. Thanks.

From rgerhards at hq.adiscon.com  Tue Nov 27 15:45:29 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Tue, 27 Nov 2007 15:45:29 +0100
Subject: [rsyslog] segfault bug
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA3084FC@grfint2.intern.adiscon.com>

Hi all,

I have just elaborated on my leading theory of the segfault bug being
related to a threading issue:

http://rgerhards.blogspot.com/2007/11/found-another-part-of-code-that-is
-not.html

However, I'd like to double check: As far as I have tracked, everyone
who experienced the segfault issue is running rsyslog in multi-threading
mode (the default). A few have changed to single-threading mode (via
./configure --disable-pthreads) and then the problem disappeared.

So I'd like to ask if someone RUNNING rsyslogd in SINGLE THREADING mode
has experienced a segfault. This is very vital information, because it
effectively pinpoints the trouble source...

Feedback is appreciated.

Thanks,
Rainer

From hagen at rz.uni-karlsruhe.de  Tue Nov 27 16:31:00 2007
From: hagen at rz.uni-karlsruhe.de (Patrick von der Hagen)
Date: Tue, 27 Nov 2007 16:31:00 +0100
Subject: [rsyslog] Looking for bughunters...
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com>
References: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com>
Message-ID: <1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>

Am Dienstag, den 27.11.2007, 10:54 +0100 schrieb Rainer Gerhards:
[...]
> Your help is deeply appreciated!
Short: won't work out of the box on RHEL5.1.

Long:
Download of RPM to RHEL5.1, installed libmudflap and libmudflabp-devel,
build and installed rsyslog, did not install the mysql-package.
Felt annoyed when I realised that the package moved /etc/rsyslog.conf
to /etc/rsyslog.conf.rpmnew and copied a new configuration
to /etc/rsyslog.conf. Changed back to my old configuration.

Did "/sbin/rsyslogd -n -o -r514 -m 0". The daemon starts and that's it.
Killed it, did "/opt/rsyslog/sbin/rsyslogd -n -o -r514 -m 0" (the
"original 1.19.10") and it logged fine. So both the command-line and the
config seem to be valid. But the modified rsyslog+mudflap just sits
there in a loop, waiting for something to happen (according to strace).


open("/etc/hosts", O_RDONLY)            = 8
fcntl(8, F_GETFD)                       = 0
fcntl(8, F_SETFD, FD_CLOEXEC)           = 0
fstat(8, {st_mode=S_IFREG|0644, st_size=234, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x2aaaaaaad000
read(8, "# Do not remove the following li"..., 4096) = 234
read(8, "", 4096)                       = 0
close(8)                                = 0
munmap(0x2aaaaaaad000, 4096)            = 0
open("/etc/ld.so.cache", O_RDONLY)      = 8
fstat(8, {st_mode=S_IFREG|0644, st_size=135025, ...}) = 0
mmap(NULL, 135025, PROT_READ, MAP_PRIVATE, 8, 0) = 0x2aaaaae7e000
close(8)                                = 0
open("/lib64/libnss_dns.so.2", O_RDONLY) = 8
read(8, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\17\0\0\0\0\0
\0"..., 832) = 832
futex(0x2aaaaacea840, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted
system call)
--- SIGWINCH (Window changed) @ 0 (0) ---
futex(0x2aaaaacea840, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted
system call)
--- SIGWINCH (Window changed) @ 0 (0) ---
futex(0x2aaaaacea840, FUTEX_WAIT, 2, NULL) = -1 EINTR (Interrupted
system call)
--- SIGWINCH (Window changed) @ 0 (0) ---
futex(0x2aaaaacea840, FUTEX_WAIT, 2, NULL


Last lines indicate some DNS-problem and in fact adding "-x" to the
commandline helps. Now I'm waiting for the next crash to send my
output^.

-- 
CU,
   Patrick.

From rgerhards at hq.adiscon.com  Thu Nov 29 11:05:38 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Thu, 29 Nov 2007 11:05:38 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>

Hi all,

in the effort to fix the segfault bug, I have just released 1.19.11 of
rsyslog. There is a single, minimal, change in that release: an
additional compiler option is set. In short, the "-pthread" option was
missing and it may be the reason for the segfault. The longer story is
here:

http://rgerhards.blogspot.com/2007/11/did-i-find-rsyslog-bug.html

I released a new version to make sure new users will find the fixed
result set. Setting that option definitely doesn't hurt. The question
now is if it helps.

So... if you experience the segfault AND you are NOT running the
instrumented build created by Peter Vrabec, I'd appreciate if you could
update and let me know the results.

If you run Peter's version AND have experienced and reported a segfault,
I'll also kindly ask you to upgrade to the new version and see what
happens.

If you run Peter's version AND have not yet experienced a segfault with
it, I'd prefer if you could continue running it, at least for a while.
Even though I may have found the bug, there is still no solid evidence
and a report from Peter's version may help provide that evidence.

If you DO NOT experience a segfault, there is no point in upgrading.
Save yourself the time ;)

Download location:
   http://www.rsyslog.com/Downloads-req-getit-lid-63.phtml

Many thanks to all for your collaboration on this issue. Your help is
deeply appreciated.

Many thanks,
Rainer

From hagen at rz.uni-karlsruhe.de  Thu Nov 29 12:18:56 2007
From: hagen at rz.uni-karlsruhe.de (Patrick von der Hagen)
Date: Thu, 29 Nov 2007 12:18:56 +0100
Subject: [rsyslog] Looking for bughunters...
In-Reply-To: <1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
References: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com>
	<1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
Message-ID: <1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>

Am Dienstag, den 27.11.2007, 16:31 +0100 schrieb Patrick von der Hagen:
[...]
> Last lines indicate some DNS-problem and in fact adding "-x" to the
> commandline helps. Now I'm waiting for the next crash to send my
> output^.
No crash so far. The load is noticably higher, but still acceptable.
Now I killed the debugging-release and used precisely the same
commandline to start the regular release, which caused some crashes
here.
As I mentioned the debugging-release had some problems with DNS, so I
can't run it the same way I usually try to run rsyslog. So I'm not quite
sure wheter or not the results can actually be compared.
Anyway, I'll try the new command-line with 1.19.10 first, if that
crashes I'll switch to 1.19.11.

-- 
CU,
   Patrick.

From rgerhards at hq.adiscon.com  Thu Nov 29 12:20:50 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Thu, 29 Nov 2007 12:20:50 +0100
Subject: [rsyslog] Looking for bughunters...
In-Reply-To: <1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
References: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com><1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
	<1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308527@grfint2.intern.adiscon.com>

Patrick,

excellent, many thanks. We stay tuned for updates. I am very hopeful for
the compiler switch issue...

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Patrick von der Hagen
> Sent: Thursday, November 29, 2007 12:19 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] Looking for bughunters...
> 
> Am Dienstag, den 27.11.2007, 16:31 +0100 schrieb Patrick von der
Hagen:
> [...]
> > Last lines indicate some DNS-problem and in fact adding "-x" to the
> > commandline helps. Now I'm waiting for the next crash to send my
> > output^.
> No crash so far. The load is noticably higher, but still acceptable.
> Now I killed the debugging-release and used precisely the same
> commandline to start the regular release, which caused some crashes
> here.
> As I mentioned the debugging-release had some problems with DNS, so I
> can't run it the same way I usually try to run rsyslog. So I'm not
> quite
> sure wheter or not the results can actually be compared.
> Anyway, I'll try the new command-line with 1.19.10 first, if that
> crashes I'll switch to 1.19.11.
> 
> --
> CU,
>    Patrick.
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From pvrabec at redhat.com  Thu Nov 29 12:35:31 2007
From: pvrabec at redhat.com (Peter Vrabec)
Date: Thu, 29 Nov 2007 12:35:31 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
References: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
Message-ID: <200711291235.31902.pvrabec@redhat.com>

Peter's version update:

http://people.redhat.com/pvrabec/rpms/rsyslog/rsyslog-1.19.11-1.mudflap.src.rpm

From mbiebl at gmail.com  Fri Nov 30 11:15:18 2007
From: mbiebl at gmail.com (Michael Biebl)
Date: Fri, 30 Nov 2007 11:15:18 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
References: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
Message-ID: <aa76cdac0711300215g6993018di85585341856fb95@mail.gmail.com>

2007/11/29, Rainer Gerhards <rgerhards at hq.adiscon.com>:
> Hi all,
>
> in the effort to fix the segfault bug, I have just released 1.19.11 of
> rsyslog. There is a single, minimal, change in that release: an
> additional compiler option is set. In short, the "-pthread" option was
> missing and it may be the reason for the segfault. The longer story is

There is a small problem:
pthreads_libs, as used in rsyslogd_LDADD, is not set anymore.
The attached patch fixes that.
I also used a separate pthreads_cflags variable which is assigned to
rsyslogd_CPPFLAGS. It's cleaner than overwriting the global CFLAGS
variable.

Please review.

Cheers,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

From hagen at rz.uni-karlsruhe.de  Fri Nov 30 11:24:26 2007
From: hagen at rz.uni-karlsruhe.de (Patrick von der Hagen)
Date: Fri, 30 Nov 2007 11:24:26 +0100
Subject: [rsyslog] Looking for bughunters...
In-Reply-To: <1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
References: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com>
	<1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
	<1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
Message-ID: <1196418266.4479.1.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>

Hi all,

just a small update: 1.19.10-debug worked for two days without problems.
1.19.10 crashed after 5 hours.
Now I'll give 1.19.11 a try....

-- 
CU,
   Patrick.

From rgerhards at hq.adiscon.com  Fri Nov 30 11:26:25 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Fri, 30 Nov 2007 11:26:25 +0100
Subject: [rsyslog] Looking for bughunters...
In-Reply-To: <1196418266.4479.1.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
References: <577465F99B41C842AAFBE9ED71E70ABA3084F1@grfint2.intern.adiscon.com><1196177460.3967.11.camel@rzm-hagen-lt.rz.uni-karlsruhe.de><1196335136.3867.17.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
	<1196418266.4479.1.camel@rzm-hagen-lt.rz.uni-karlsruhe.de>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308552@grfint2.intern.adiscon.com>

Patrick,

ok - even though this sounds somewhat silly, I think this is good news.
It is evidence that the problem is not related to the option. That, too,
points into the direction of a threading issue, so it is consistent with
former findings. 

What I now hope is that the rest of the analysis is true, too. In that
case, 1.19.11 should work...

Thanks for all your help. Much appreciated.
Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Patrick von der Hagen
> Sent: Friday, November 30, 2007 11:24 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] Looking for bughunters...
> 
> Hi all,
> 
> just a small update: 1.19.10-debug worked for two days without
> problems.
> 1.19.10 crashed after 5 hours.
> Now I'll give 1.19.11 a try....
> 
> --
> CU,
>    Patrick.
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From rgerhards at hq.adiscon.com  Fri Nov 30 11:29:45 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Fri, 30 Nov 2007 11:29:45 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
In-Reply-To: <aa76cdac0711300215g6993018di85585341856fb95@mail.gmail.com>
References: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
	<aa76cdac0711300215g6993018di85585341856fb95@mail.gmail.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308554@grfint2.intern.adiscon.com>

Ah, excellent. Once more I have to admit that I am not a tools guy ;)

And, as usual, the mailing list is very picky - the attachment was
stripped. Can you send it via private mail, I can host it on
rsyslog.com.

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Michael Biebl
> Sent: Friday, November 30, 2007 11:15 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog 1.19.11 released
> 
> 2007/11/29, Rainer Gerhards <rgerhards at hq.adiscon.com>:
> > Hi all,
> >
> > in the effort to fix the segfault bug, I have just released 1.19.11
> of
> > rsyslog. There is a single, minimal, change in that release: an
> > additional compiler option is set. In short, the "-pthread" option
> was
> > missing and it may be the reason for the segfault. The longer story
> is
> 
> There is a small problem:
> pthreads_libs, as used in rsyslogd_LDADD, is not set anymore.
> The attached patch fixes that.
> I also used a separate pthreads_cflags variable which is assigned to
> rsyslogd_CPPFLAGS. It's cleaner than overwriting the global CFLAGS
> variable.
> 
> Please review.
> 
> Cheers,
> Michael
> 
> 
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?

From mbiebl at gmail.com  Fri Nov 30 12:02:29 2007
From: mbiebl at gmail.com (Michael Biebl)
Date: Fri, 30 Nov 2007 12:02:29 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA308554@grfint2.intern.adiscon.com>
References: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com>
	<aa76cdac0711300215g6993018di85585341856fb95@mail.gmail.com>
	<577465F99B41C842AAFBE9ED71E70ABA308554@grfint2.intern.adiscon.com>
Message-ID: <aa76cdac0711300302s645ad9c1mbc8aa00e1f84bf62@mail.gmail.com>

2007/11/30, Rainer Gerhards <rgerhards at hq.adiscon.com>:
> And, as usual, the mailing list is very picky - the attachment was
> stripped. Can you send it via private mail, I can host it on
> rsyslog.com.

Oh, sorry. I forgot...
Here it is:
http://debs.michaelbiebl.de/rsyslog/0001-pthreads-cflags-proper.patch

Cheers,
MIchael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

From mbiebl at gmail.com  Fri Nov 30 13:35:38 2007
From: mbiebl at gmail.com (Michael Biebl)
Date: Fri, 30 Nov 2007 13:35:38 +0100
Subject: [rsyslog] Please remove autogenerated files from CVS
Message-ID: <aa76cdac0711300435u6927667eud766cb7e8f1ffba7@mail.gmail.com>

Hi,

aclocal.m4 and depcomp are automatically created when I build the
autotools support (by running autoreconf -vfi), so they should be
removed from CVS.
Most developers will have different version of autoconf/automake, so
these files will be listed as modified, which is a bit annoying.

Having .cvsignore files would be nice, too:
== .cvsignore ==
.deps
.libs
Makefile
Makefile.in
autom4te.cache
config.guess
config.h
config.h.in
config.log
config.status
config.sub
configure
libtool
ltmain.sh
aclocal.m4
depcomp
stamp-h1
rfc3195d
rklogd
rsyslogd

== doc/.cvsignore ==
Makefile
Makefile.in

== plugins/ommysql/.cvsignore ==
.deps
.libs
Makefile
Makefile.in
ommysql.la
ommysql_la-ommysql.lo


Cheers,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

From rgerhards at hq.adiscon.com  Fri Nov 30 14:16:13 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Fri, 30 Nov 2007 14:16:13 +0100
Subject: [rsyslog] Please remove autogenerated files from CVS
In-Reply-To: <aa76cdac0711300435u6927667eud766cb7e8f1ffba7@mail.gmail.com>
References: <aa76cdac0711300435u6927667eud766cb7e8f1ffba7@mail.gmail.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308555@grfint2.intern.adiscon.com>

Michael,

thanks again for the good advise. Patch applied, files removed,
committed to cvs. Note that I branched for 1.19.11, because there are
already a number of changes in what will become 1.20.1 (GSS-API, clean
module unload interface). The branch for 1.19.11 and above is
v1-19-1_branch. I thought it would contain just one release ;)

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Michael Biebl
> Sent: Friday, November 30, 2007 1:36 PM
> To: rsyslog-users
> Subject: [rsyslog] Please remove autogenerated files from CVS
> 
> Hi,
> 
> aclocal.m4 and depcomp are automatically created when I build the
> autotools support (by running autoreconf -vfi), so they should be
> removed from CVS.
> Most developers will have different version of autoconf/automake, so
> these files will be listed as modified, which is a bit annoying.
> 
> Having .cvsignore files would be nice, too:
> == .cvsignore ==
> .deps
> .libs
> Makefile
> Makefile.in
> autom4te.cache
> config.guess
> config.h
> config.h.in
> config.log
> config.status
> config.sub
> configure
> libtool
> ltmain.sh
> aclocal.m4
> depcomp
> stamp-h1
> rfc3195d
> rklogd
> rsyslogd
> 
> == doc/.cvsignore ==
> Makefile
> Makefile.in
> 
> == plugins/ommysql/.cvsignore ==
> .deps
> .libs
> Makefile
> Makefile.in
> ommysql.la
> ommysql_la-ommysql.lo
> 
> 
> Cheers,
> Michael
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog

From rgerhards at hq.adiscon.com  Fri Nov 30 14:31:36 2007
From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Date: Fri, 30 Nov 2007 14:31:36 +0100
Subject: [rsyslog] rsyslog 1.19.11 released
In-Reply-To: <aa76cdac0711300302s645ad9c1mbc8aa00e1f84bf62@mail.gmail.com>
References: <577465F99B41C842AAFBE9ED71E70ABA30851F@grfint2.intern.adiscon.com><aa76cdac0711300215g6993018di85585341856fb95@mail.gmail.com><577465F99B41C842AAFBE9ED71E70ABA308554@grfint2.intern.adiscon.com>
	<aa76cdac0711300302s645ad9c1mbc8aa00e1f84bf62@mail.gmail.com>
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308556@grfint2.intern.adiscon.com>

I just noticed one other thing: the ommysql.c is being generated by its
own makefile (we changed that a few releases down the road). However,
that means that makefile must also be compiled with -pthread -
otherwise, run time library calls in it may fail on reentrancy. I am
right now changing this. I will not re-issue the release. Will do
together with the other things as 1.19.12, but let's wait for some
feedback first... 

Rainer

> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Michael Biebl
> Sent: Friday, November 30, 2007 12:02 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] rsyslog 1.19.11 released
> 
> 2007/11/30, Rainer Gerhards <rgerhards at hq.adiscon.com>:
> > And, as usual, the mailing list is very picky - the attachment was
> > stripped. Can you send it via private mail, I can host it on
> > rsyslog.com.
> 
> Oh, sorry. I forgot...
> Here it is:
> http://debs.michaelbiebl.de/rsyslog/0001-pthreads-cflags-proper.patch
> 
> Cheers,
> MIchael
> 
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog