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
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