> > Note: RFC3195 is NOT RELP. 3195 is a very early and (for practical > > reasons) now-abandoned syslog standard by IETF. RELP is a > > "proprietary" "standard" but well-alive ;-) > > Aha! Thanks for clarification. So, if I want to send messages through > RELP, I have to use librelp?
I checked to be sure: currently there is no RELP channel driver. The base idea was that liblogging-stdlog provides a route to file/journal/unix socket and rsyslog picks up things from the unix socket and then forwards it via RELP. This is superior to a channel driver, because this makes operation async, which usually is what you want. If you need some more info on the overall idea, let me know. I'd do a small prep (maybe we can jump into a short conf call, looks like you are in EU time zones which should make that fairly easy. If we take that route, I'd like to record so others can benefit as well. Comments appreciated. Rainer _______________________________________________ rsyslog mailing list https://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
