Heya,
ok this is the story......i host several muds on my server for people.
therefore i give them a port for the mud to run on and a port to give them ftp access to their files.
everything is great except 1 thing. if the builders crash the mud by accident then they cant reboot it. is there a way they can reboot it (remotely)? if theres a handy file someplace then please let me know.
thanks
best way to handle that is give them a shell acct to their directory so they can run the startup script themselves. Otherwise yer pretty much stuck restarting the MUD for them.
ok well - they have been able to use cygwin to access their folder but what command do they do to run it. they have tried rom.exe 7050 . but it says command unknown or something
or do you mean a windows shell?
Hrm... they may just be screwed on a windows box. I made the mistake of assuming you were hosting on a *nix machine since theyre generally prefered for anything more than a single mu*. As for Windows, you would have to give them remote access accounts and enough priveledges to execute commands on your machine, generally NOT a good idea since windows security is such a joke. As for what they would need to run, normal startup command for their mud, whatever that might be.
It may be that you have to type in ./ before your exe command. This is a feature that some *nix boxes use to make sure you really mean to run a given executable, and I think Cygwin inherits it. I know that when I restart my MUD (on a true Linux system) I need it.
If the exe is rom.exe, they maybe have to type ./rom 7040 (if that's what the port was), or perhaps ./rom.exe 7040. They'll need executable privileges on the file as well.
Here's what I type:
nohup ./startup 5432 > nohup.out 2>&1 &
Where startup is a shell script that I believe is standard. The nohup part makes it not die when I log out (generally a useful thing :P).
The other thing you could do is set up an automatic restart. There is a small program in the utilities area here (I think) that does that. Basically it checks every minute or so if the MUD is up (by trying to bind to the port) and if it is (ie. the port is in use) then it does nothing, otherwise it runs a command you define (ie. the command to restart the MUD).
If you set that up then you don't need to give anyone access, just have it check every 5 minutes (don't make it too quick or you might get a 2nd copy while the first is reading in its area files). This will be quicker anyway than waiting for an admin to wake up, log on, etc.