I forgot to mention: > Well, I think the key thing is try to setup some lab where the crashes happen > as well. I guess it is either message-induced or induced by some issues in > Solaris threading. Maybe it helps if you record traffic (from sufficient > sources) and replay it against a Linux box. If that one crashes, we have more > options. If it does not crash, this does not directly point us to something, > unfortunately...
What I am looking for is some better information on when the crash happens. So valgrind is often a good choice to check if there are some violations. Not sure, though, if that's available on Solaris. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
