On Wed, Sep 25, 2013 at 5:44 PM, Jon Schipp <[email protected]> wrote:

> Ah, I was under the impression that you could use both TCP and RELP on the
> same port number should you have some clients using one and not the other.
> That resolved it. Thanks a bunch Alan
>
> Also, no, when starting rsyslogd the logs only show:
> Sep 25 10:37:24 relay02-sec rsyslogd: [origin software="rsyslogd"
> swVersion="7.4.4" x-pid="5868" x-info="http://www.rsyslog.com";] start
> Sep 25 10:37:24 relay02-sec rsyslogd-2184: action '*' treated as
> ':omusrmsg:*' - please change syntax, '*' will not be supported in the
> future [try http://www.rsyslog.com/e/2184 ]
>
>
there seems to be a problem in imrelp. If imtcp is loaded before imrelp, no
error message is emitted. The other way around it is. Will see what I can
do.

Rainer
_______________________________________________
rsyslog mailing list
http://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.

Reply via email to