On Mon, 4 Apr 2005, Isaac Richards wrote: > On Monday 04 April 2005 03:48 pm, Brian Foddy wrote: > > From what I have seen, the first offending bad command is actually a > > blank or null message. The UNKNOWN_COMMAND message starts appearing > > after a few cycles. I've tried to find a common point in the sending > > command logic to trace all sent commands, but it seems like they can > > originate from serveral locations in code. But I'm almost wondering > > if the original message is actually a phantom or left-over fragment > > that is being taken as a new message. > > That's possible. Could try making it ignore blank messages, but if > whatever's > sending them is waiting on a reply, that'll cause problems. >
That's what I was afraid of. I tried sending an "OK" instead of the UNKNOWN_COMMAND, but that caused the loop as well. I also noticed some places its "OK" others its "ok" (lower case). Significant? > > If someone knows of a central stop to log sending commands, that would > > help greatly... > > Really isn't one, except in util.cpp. > If I could log the whole conversation, then we'd at least know if its a real command or a fragment. I suppose I could ethereal the network communication. Would this help? Any other ideas? Which port would I want to watch? Brian
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
