Thanks David for the response. Our use-case involves imudp (UDP reception of syslog messages), imuxsock and imklog. The major config changes expected are w.r.t remote server logging details.
We are evaluating if there is any way to alleviate the possible loss of messages when rsyslog is restarted due to a change in the configuration file. We were evaluating if there is a chance of keeping the input modules running to avoid this loss while parts of rsyslog may restart due to a new configuration. I understand this in itself may be a herculean task considering the interdependencies and config being tied together. Could you please provide inputs on the above approach? Also, it looks like there was a text API based interface you had proposed to allow some basic runtime-config changes to rsyslog (http://rsyslog-users.1305293.n2.nabble.com/making-config-changes-to-a-running-rsyslog-td7591667.html). Could you please elaborate on the same as well? -- Sent from: http://rsyslog-users.1305293.n2.nabble.com/ _______________________________________________ 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.
