What I had in mind was something like an SCTP stream for each log level or each facility, haven't decided which would be most useful. That prevents head-of-line blocking as happens in TCP. So, for example, if a buffer is full of DEBUG level messages, an ALERT level message would go immediately as it is in a different stream. A separate stream could be added for RELP messages (or something like RELP or maybe an extension of it) and all of these streams would be within a single SCTP connection. Or maybe you can send RELP-like messages back across each stream in the opposite direction but having an "out of band" control channel sounds like an interesting idea and something fairly easy to do with SCTP.
I would also think this lends itself well to threading of the different streams with a different thread handling different log levels (or facilities but I think dividing among log levels is probably easier). On an SMP system, a remote host sending a lot of DEGUG level messages while it is being tested would bog down one thread but other messages would be processed separately without network head-of-line blocking or CPU blocking (disk contention would be a different story, though ;) > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of George Bonser > Sent: Saturday, April 24, 2010 11:20 AM > To: rsyslog-users > Subject: [rsyslog] Syslog over SCTP? > > Has anyone experimented with using SCTP for logging to a remote host? > It seems it might have some advantages over TCP and UDP for that > purpose. > > http://www.ibm.com/developerworks/linux/library/l-sctp/ > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
