maybe something for Damien. It could be nice, to start and stop the spawners at network machines. So, the user could restart a crashed spawner or if something dosn’t work right, he could restart a spawner.exe per stop&start.
A tool for this wish could be the pstool from here
If psexec dosn’t work, than it helps to deactivate the simple file access (I’m not sure how it looks at an english system), here the german hint I found
Im Explorer muss unter Extras->Ordneroptionen->Ansicht “einfache Dateifreigabe verwenden” deaktiviert werden. Dann lief alles und die Fehlermeldung “Zugriff verweigert” erschien nicht mehr.
Not for me…there’s nothing I can really do with the spawners. I’m not really sure what your asking for anyway…can you explain further because I’m not getting it.
It could be nice, if a Rhino button could be used, to restart the spawner.exe at the slave engines.
Example: a spawner is crashed at a slave or hanging - could be nice, if from within Rhino, it could be restart. At the moment, the user must use a remote software and manualy start the spawner.exe.
The pstools allow to kill and start programms at other engines. I thought, a Rhino programmer could use it to kill&start the spawner.exe from within Rhino.
Yeah, i too have asked Joe if he could release a System Service version of the spawner. Perhaps as a service some remote console commands could be added.
I like to sneak it on peoples machines here in the office. It’s not uncommon to hear “WTF, Who’s stealing all of my threads!?”
Well, still not me…That doesn’t sound like too bad of an idea though, although off the top of my head, I’m not sure how that could be done from a network security standpoint (most will prevent an remote connection from starting up an exe).
A service would solve the problem. it could intercept the start and stop command to boot the spawner and prepare it to render as well as restart it. The service itself just sits and waits to be told what to do.
You could also set it up so that the console is not visible on the remote machine as well.
It’s really a fairly simple task. Maybe sometime in the near future when i get a little bit of down time, i’ll write a service that shells it and kills it along with a remote app that sends a little tcp/ip string to boot it, stop it, and restart it.
Today I found some time to play with the microsoft tools and now I can kill the spawner at the slave engine and restart it. A simple bat file at the master contain:
Funny, if the option -i isn’t use, than the new started spawner console isn’t visible at the slave, it’s shown at the master, but the slave is full running. So, the spawner can started at every computer at the network without the user at this computer must see it.
Now I can start my bat file per Rhino button for killing and restart the spawner. The short button script is
_run "C:\Documents and Settings\Administrator\Desktop\PSTools\kill.bat"
the -i option is most likely stands for interface. Basically most apps can be started with or without their interface. Starting it without helps out with memory since UI doesn’t have to be created or drawn. This is also helpful with doing certain things “silently”
Little update: this batch file code kill the spawners at three slave engines and restart the spawners. If I start the batchfile per Rhino button, than it dosn’t full work. The spawners are killed, but not restarted. Any idea why it dosn’t work like a manual batch file start?
I asked Vlado a couple days ago for some information on the way DR was implemented. I would really like to add to the existing functionality. Particularly a batch rendering / render queue for distributed and network rendering. Also a way to have nodes join renders on the fly instead of only being used if they are available at the very beginning of the render sequence.
But yeah - I would like to be able to give more precise control over the dr stuff. When Vlado opens up some of the SDK to us then we should be able to make some cool improvements. So keep your fingers crossed
Re: Run and Stop spawner at network computers without remote install
I found a little free tool that allow me to open all my console windows within one window. Also now I can choose from selfdefined presets like info/startall/killall/suspendall. ;D
allow to start the console with three Tabs, which started spawners at all my Slaves.
Also, now it’s possible to start, kill, suspend and shutdown all slaves per Rhino buttons. A Rhino button command must be linked to the shortcut with the right started tabs. Example of a Button script for start all spawners:
Re: Run and Stop spawner at network computers without remote install
Today I found, that it is possible to get some interesting infos about the drspawner per PS Tool pslist. I wrote a little batch file, that show me the infos of all spawners:
The value Priv shows the current used memory of the DRspawner, in my case approx. 1.8GB. Most important for me, this info batch script allow me to check, is a DRspawner running or not.
It could be nice, to start and stop the spawners at network machines. So, the user could restart a crashed spawner or if something dosn’t work right, he could restart a spawner.exe per stop&start.
