On Mon, 2 May 2016, [email protected] wrote:
Hi,I've a /etc/rsyslog.d/app.conf that creates a logging socket. If for whatever reason I need to recreate that socket, I know I can do that by restarting 'all' of rsyslogd. Is that needed? Is there a less invasive method? Maybe to just restart/re-exec that one logging instance? Or cmd-line recreate that socket, making sure rsyslogd is aware of the change?
you may be able to create the socket and then HUP rsyslog, but I'm not sure if that will make it see it correctly or not. Check with lsof to make sure that rsyslog has the correct socket open after the HUP
If this doesn't work, a full restart will be needed. 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.
