|
Post by Jerry Muelver on May 23, 2009 6:54:20 GMT -5
And as soon as you miss to close a file correctly again, this issue will come up again. And always having Jerry to reboot your server manually is not the best option. I think it would be much more comfortable, if users could do it themself. Aside from giving everyone Remote Desktop access to the server ( ), I wouldn't know how to do that. It's like, if you lock your car keys inside the car, you can use your car keys to open the door to get your car keys.....
|
|
|
Post by votan on May 23, 2009 7:47:47 GMT -5
Right now I'm using shell$ to access a dos tool that fetches all active processes. I then parse the output and only list one instance of RB that is run by the user currently trying to reboot his RB instance. This I do by comparing pathes of the process with the default path of RB. I then call a dos batch and pass all needed parameters to it. This will close the correct process and then restarts it. It works so far.... but when doing it all through a website, the batch can not restart the server. This is because of access rights and I have to figure out a workaround for this. I'm working on it.. it's just not as easy as I thought...
|
|
|
Post by StefanPendl on May 23, 2009 8:57:14 GMT -5
You can use AT to start the batch file after a minute, so it is not running in the context of the current process.
|
|
|
Post by votan on May 23, 2009 10:42:26 GMT -5
Nice tip! didn't even know that command. Am right now tricking the system with CPAU www.joeware.net/freetools/tools/cpau/index.htm, but doing it with AT would be much nicer. I'll try it tomorrow, when I hopefully have some time for it.
|
|
|
Post by StefanPendl on May 23, 2009 11:32:03 GMT -5
The beauty of AT is, that it is available on Linux hosts too.
Windows XP and above include the enhanced version SchTasks, but using AT will make this cross-platform compatible.
|
|
|
Post by Carl Gundel - admin on May 23, 2009 21:53:41 GMT -5
So far so bad.... The RB server is not behaving as it should! the restarted server always listens on the default port 8008, while the config file says 8080. So it seems like the restarted version can not read the config file and so starts on the default port that is set somewhere in the RBserver code itself. Carl.... is there an additional command line parameter to define the configfile to start with? So like c:\rbp\rbp.exe tb.im config.xml ? But whatever, I'll get it to work... might need it for a futere project as well.. Hi, I was not able to reproduce this. When I edit the port manually and restart or by using the Preferences tab it does work for me. Are you still seeing this? -Carl
|
|
|
Post by votan on May 24, 2009 2:49:36 GMT -5
It was just a path settings problem of DOS when launching RB via a batch file. Had to do a CD into the RB dir instead of calling RB directly by using c:/rbp/rbp.exe. Without doing that, RB can not fetch the settings file.
|
|