Hi,
I'm wondering about how and if at all RSyslog handles voluntary stop signals: TSTP. I have not been able to find any concrete information on this, but maybe my google-fu is weak. If there is no voluntary stop handling, how about mandatory stop signals: STOP? How will the program behave? My expectation is that it will not handle any incoming messages, and in the case of UDP they will be lost. I'm running RSylog 7.4.4 on x86_64 embedded Linux. The reason I'm wondering this is because I have the need to move the location rsyslog writes to during the boot phase. RSylog is started early in the boot phase, when this particular system has no persistent storage area mounted - the logs go into ramdisk. Later in the boot phase network storage is attached. At this point, I would like to be able the halt RSyslog from writing to file, so that the logs on ramdisk can be moved, and then continue to be appended at the new location. Just sending a HUP signal to rsyslog could cause out of order or lost logs, depending on the order of doing move compared HUPing. Any ideas on this would be much appreciated. Best Regards Anders _______________________________________________ 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.
