I've got around 150 wireless access points on my network and would like to be able to run a query on all of them... I've been using the MXP "relocate" tag to do my own queue logic and query one at a time, but it would be nice if there were some built in way of hitting all the servers in batches of 10 or something and having the one or two lines of output I care about in the final window. If I don't get the lines I want, I'd like the process to halt and the window be displayed for manual intervention. If I get the lines I want, the session should be terminated and it's window closed.
You get what I mean? It's a poor man's way for querying or changing config enterprise-wide. :)
It's a little easier to justify a TeSSH license or two to the boss than the likes of HP OpenView/etc!
Feature request: Run-on-multiple
Feature request: Run-on-multiple
Mon, 04/11/2011 - 4:30pm
#1
Wed, 04/13/2011 - 9:42am
#2
Do you need to run a SSH shell command on the access points, or is some information available via HTTP? If they have something via HTTP then you can try the %url function to retrieve the data.
Also seems like using the MXP RELOCATE is also workable and you should be able to integrate that into a script that does what you want. Or in a separate window you can try the #SESSION command to connect to a different SSH address and then run a script. Again, seems like something that you can already script so I'm not sure what else I would add to support this.
Doing it in some sort of batch would make it difficult to halt in the proper session if a problem was found. Certainly sounds a bit to specific to your situation to warrant a new feature, so try the above script ideas to see what you can come up with.
You might want to try posting this over in the CMUD Discussion Forum on www.zuggsoft.com since the scripting of TeSSH is the same as CMUD and there are more people on the CMUD forums that might have some scripting ideas on this.
Also seems like using the MXP RELOCATE is also workable and you should be able to integrate that into a script that does what you want. Or in a separate window you can try the #SESSION command to connect to a different SSH address and then run a script. Again, seems like something that you can already script so I'm not sure what else I would add to support this.
Doing it in some sort of batch would make it difficult to halt in the proper session if a problem was found. Certainly sounds a bit to specific to your situation to warrant a new feature, so try the above script ideas to see what you can come up with.
You might want to try posting this over in the CMUD Discussion Forum on www.zuggsoft.com since the scripting of TeSSH is the same as CMUD and there are more people on the CMUD forums that might have some scripting ideas on this.
Thu, 04/14/2011 - 11:22pm
#3
Unfortunately the web GUI is all done in a java applet, so we have to use SSH to query it!
I didn't have much luck with #SESSION a few years ago when I was doing this inside CMUD with older hardware (telnet based). I think it spawned a new session fine, but it didn't have my scripts or something? I will have to tinker a bit more with TeSSH and see how it goes.
I was just thinking it would look nice with a main session and 150 different progress bars and then windows in the background which scroll away as they do the query, then the progress bars either go green because the query was successful, or red because something wrong happened. I'll have to investigate... maybe I could write a .NET app which spawns multipe TeSSH's... "tessh 192.168.0.1" have it run a bunch of triggers and at the end calls #MENU {File|Exit}
Hmmm....
Anyway, going on holiday for a few weeks! I'll have a tinker when I get back to it :)
I didn't have much luck with #SESSION a few years ago when I was doing this inside CMUD with older hardware (telnet based). I think it spawned a new session fine, but it didn't have my scripts or something? I will have to tinker a bit more with TeSSH and see how it goes.
I was just thinking it would look nice with a main session and 150 different progress bars and then windows in the background which scroll away as they do the query, then the progress bars either go green because the query was successful, or red because something wrong happened. I'll have to investigate... maybe I could write a .NET app which spawns multipe TeSSH's... "tessh 192.168.0.1" have it run a bunch of triggers and at the end calls #MENU {File|Exit}
Hmmm....
Anyway, going on holiday for a few weeks! I'll have a tinker when I get back to it :)
Tue, 09/06/2011 - 4:49pm
#4
Ok... so I've finally got my script working-ish.
I use the MXP relocate command to change servers, but I'm running into a problem with the auto-connect prevention... that after 20 or 40 (not sure which) relocates it thinks you've exceeded the auto retry timeout and you have to manually click the retry button.
I know you put that feature in to stop players from continually hitting the MUD's, but could we maybe get a way to change it from the hard-coded value of 20/20 to whatever limits we want (just in TeSSH/CMUDPRO)?
I use the MXP relocate command to change servers, but I'm running into a problem with the auto-connect prevention... that after 20 or 40 (not sure which) relocates it thinks you've exceeded the auto retry timeout and you have to manually click the retry button.
I know you put that feature in to stop players from continually hitting the MUD's, but could we maybe get a way to change it from the hard-coded value of 20/20 to whatever limits we want (just in TeSSH/CMUDPRO)?
Copyright © 2024 by 