[syslog-ng] syslog-ng and solaris again

Hi, I further inverstigated the Solaris problem. Any door calls arriving to syslog-ng contain NULL as the log message. I tried to call the door using my small .c program, and it was successful, and the message arrived without problems. So solaris is playing some nasty games here. If this problem is solved, there's still one thing to be resolved: I must interrupt the poll() syscall when a message arrives from a thread (because destinations are written in nonblocking fashion, and when poll() was called the buffered output was not yet available, the thread changes this state, but poll will not know this, another solution would be to use a pipe to communicate with the nonblocking i/o layer from the threads. -- Bazsi