Re: How to change the sessiontimeout of subagent agentx message

> On Mon, 22 Nov 2010 12:18:09 +0530 (IST), Sathish Chandrasekaran > said: SC>    Thanks for your response.Is this token supported for subagent SC> mode -"agentXTimeout" Iam getting warning as unknown Token  for SC> -"agentXTimeout" ,when I add this in the config file.BTW, Iam using

Re: Negative "request id" as perceived by wireshark and/or agents

> On Sun, 21 Nov 2010 17:17:45 -0500, Doug Manley > said: DM> This made absolutely no sense to me and I almost never caught it Unfortunately there is pretty much no way to determine what the cause might be without you running your daemon in a debugger. The only possibility I can think

Re: Negative "request id" as perceived by wireshark and/or agents

WH> Unfortunately there is pretty much no way to determine what the cause WH> might be without you running your daemon in a debugger. I'll see what we can do about that. WH> The only possibility I can think of is if you're actually succeeding in WH> wrapping a 16bit int (IE, you have a request ou

Re: Negative "request id" as perceived by wireshark and/or agents

One more thing; I now recall that we were getting crashes [that could not be reproduced with valgrind] on single processes that ran for about 1-10 seconds and only sent no more than 1000 requests. It was *that* behavior that led me to "16bitIDs yes". I'll look at the other variables that get 16-b