|
Author Topic:   LDA Community servers and logscan are back up but..
KiLlEr
Member
posted March 24, 2004 11:31 AM            
Jim didn't enable the Web Command system in LogScan.

documentation excerpt:

quote:

There are 2 menu items to control this feature in TMLogScan.

Set Web Command Port Number - sets the port number used by Web Command (default port is 10000).
Enable/Disable Web Command Listener - enable/disable the Web Command feature (default is disabled).


Without it, the community server admins cannot use the newer system to control the servers. They'll have to use the older passive system.

[This message has been edited by KiLlEr (edited March 24, 2004).]

IP:

LDA
Administrator
posted March 24, 2004 11:52 AM            
Got it

Jim

IP:

KiLlEr
Member
posted March 24, 2004 01:27 PM            
Sweet deal!

Thank you Jim!

IP:

Blue n Gold Sue
Member
posted March 24, 2004 08:28 PM            
Yesss, thank you JIM!

IP:

666
Member
posted March 25, 2004 01:19 AM            
now...is one of you two would explain it to me...then maybe I can use it...LOL

IP:

KiLlEr
Member
posted March 26, 2004 10:45 AM            
Oops I missed that post.

Check out the 'readme.txt' file in your TMLogSCan directory. It explains what each command on the WebCommand panel does (in your MyBoomstick account). Its not much different than what you currently use to enable/disable servers.

I'll modify the LDA community server select panel to use the WebCommand system instead of the passive system to bring up a community server.

[This message has been edited by KiLlEr (edited March 26, 2004).]

[This message has been edited by KiLlEr (edited March 26, 2004).]

IP:

KiLlEr
Member
posted March 26, 2004 12:02 PM            
Done, the LDA community server selection now uses WebCommands and is being audited.

[This message has been edited by KiLlEr (edited March 26, 2004).]

IP: