Bugzilla – Bug 630
CLI doesn't handles all commands, needs empty \n to flush
Last modified: 2008-12-18 11:52:17 UTC
Connect to 9090, send a bunch (7 for example) of commands. You get a few results (3, 4) then nothing, until you send another command (or a single \n) at wich point you get the rest of the answers. Example: $ telnet slimserver 9090 [ then paste this list of commands (that assume you have two players...): player count ? player id 0 ? player id 1 ? player name 0 ? player name 1 ? player ip 0 ? player ip 1 ? ] [ You receive: player count 2 player id 0 00%3A04%3A20%3A05%3A65%3Aba player id 1 50%3A46%3Ad0%3A12%3Ae9%3A77 player name 0 Lounge ] [ You then type return just once, and get: player name 1 Yelp player ip 0 10.0.0.25%3A39368 player ip 1 10.0.0.3%3A55818 ] So it pretty much prevent that interface to work properly, as you have to send regular \n packets to get the oupout in case it's "stuck"
Seems to be a Windows server issue. Can't reproduce that on a Mac OS 5.4.x server.
This should be fixed in the 6.0 beta. Please verify and reopen if it's still an issue.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.