On Fri, Oct 25, 2013 at 1:08 PM, David Lang <[email protected]> wrote: > On Fri, 25 Oct 2013, C. L. Martinez wrote: > >> Hi all, >> >> I am using rsyslog 7.4.4 on my syslog collector servers. Sometimes, >> syslog receptors are not online (due to maintenance tasks for >> example). Is it possible to flush logs queued by rsyslog and send them >> to receptors without restarting rsyslog? > > > I don't know that I fully understand your situation, but given that a HUP > causes rsyslog to close and re-open it's outputs, that may trigger a queue > that was waiting because of a problem to start delivering again. >
Nop, it doesn't works: root@sip01:/data/rsyslog # ls -al total 19990 drwxr-xr-x 2 root wheel 3 Oct 25 03:18 . drwxr-xr-x 7 root wheel 512 Oct 24 08:41 .. -rw------- 1 root wheel 20429847 Oct 25 03:25 fort_fwd.00000001 root@sip01:/data/rsyslog # cat /var/run/rsyslog.pid 85340 root@sip01:/data/rsyslog # kill -HUP 85340 root@sip01:/data/rsyslog # ls -al total 19990 drwxr-xr-x 2 root wheel 3 Oct 25 03:18 . drwxr-xr-x 7 root wheel 512 Oct 24 08:41 .. -rw------- 1 root wheel 20429847 Oct 25 03:25 fort_fwd.00000001 _______________________________________________ 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.
