On Sat, 24 Jan 2015, singh.janmejay wrote:
That is alright. I wanted to float the idea and get an agreement. I'll be happy to implement it, if we see value in it.
Let's back up here and talk about the problem rather than getting bogged down in the solution.
Rsyslog already has the ability to relay the message from one machine to another reliably, the problem you are trying to address is what happens if the box dies after the receiving machine acks the message, correct?
Currently we can (at a performance cost) configure the receiving machine to ack the message only after it's safe on redundant disks, but the message still won't be delivered until after the machine is repaired (worst case)
You are looking for a way to deal with this problem. Is this a reasonable problem statement? 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.
