4 Mar
2011
4 Mar
'11
10:41 a.m.
Hi, I've found a problem in handling context-timeout in a special case. If context-timeout=10 (10 sec) and I am using a trigger, where trigger="timeout", it can happen that the timeout won't expire: I sent the following two messages to syslog-ng before expiring timeout (but the difference between the two timestamp is bigger than the timeout value): "<38>1990-01-01T14:45:25 customhostname program6[1234]: program6 testmessage" "<38>1990-01-01T14:55:25 customhostname program6[1234]: program6 testmessage" I receive the timeout message immediately, when the second message arrives (it's ok), but there is no timeout for the second message.