On Fri, 30 Dec 2016, Dmitriy Kalinin via rsyslog wrote:
one alternative to above approach is to keep on reloading rsyslog every x seconds while rewriting rsyslog config to include all found nested directories within one directory. this feels somewhat wrong given that imfile seems to lean towards wildcard support (just current impl is limited). aside from feeling a bit awkward are there any downsides to reloading rsyslog every x seconds (of course we can add some kind of config file hashing to see if reload is necessary -- not sure if rsyslog already does that by default)? will reload interfere with loaded forwarding rules for existing files (especially if files are being logrotated at the same time)?
The first thing would be to check if a full restart is needed or if a HUP is enough.
A full restart can take a noticable amount of time, and can cause you to loose messages because rsyslog wasn't listening (especially with UDP, but also with TCP)
so your issue is that the directories that you want rsyslog to watch don't exist at the time rsyslog is started, correct?
it sounds like what you are looking for is https://github.com/rsyslog/rsyslog/issues/1280
it's listed as a useful enhancement, sponsorship of new features is the fastest way to get them implemented (either by having someone write and submit the feature, or by paying a professional services contract with adiscon). It's usually not very expensive to do so.
David Lang _______________________________________________ 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.
