Hi rsyslog-comunity, I have this snippet at the and of the default CentOS7 rsyslog.conf.
$ActionQueueFileName pipeRule1 $ActionQueueMaxDiskSpace 1g $ActionQueueSaveOnShutdown on $ActionQueueType LinkedList $ActionResumeRetryCount -1 local6.* |/opt/alarmfifo Let's say I have script that sends 2000 messages with local6.error priority. I will send them several times and after that I will "cat" that pipe or read it somehow. When I check the messages, some are missing or they are not in order. Is this expected? I added two scripts. The first one is generating messages and the second one is checking the continuity or discontinuity. Actual results (when messages are queued): perl discontinuity.pl -c -i /opt/alarmfifo Starting sequence at 1 paused at 866 Discontinuity: 866 -> 870 resumed 870 paused at 1720 Discontinuity: 1720 -> 868 resumed 868 Discontinuity: 868 -> 1365 paused at 2000 Discontinuity: 2000 -> 1722 resumed 1722 Discontinuity: 2000 -> 1 paused at 582 Discontinuity: 582 -> 584 resumed 584 paused at 1364 In case of instant reading of pipe the output looks OK. Starting sequence at 1 paused at 2000 Discontinuity: 2000 -> 1 resumed 1 paused at 2000 Discontinuity: 2000 -> 1 resumed 1 paused at 2000 -- -- --------------------------------------------------------- Radovan Sroka Associate Software Engineer | Security Technologies | Red hat, Inc.
2ksyslog.sh
Description: application/shellscript
discontinuity.pl
Description: Perl program
_______________________________________________ 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.
