Top Mud Sites Forum - View Single Post

thelenian · 07-21-2002, 08:44 AM

The simplist approach I can think of would bypass system calls completely. Just do message passing through a file. It's sort of a kludge, but it gets the job done.

All you need is a perl script running in the background that continually checks for the existance of a certain file. If the file exists, the script executes whatever checks are necessary to ensure that it's a valid boot attempt, calls the boot script., and then deletes the file.

The command to reboot the MUD from the test port would simply create the file that the script checks for.

This will work even if your test MUD is on a different account, as long as the script is running with the proper permissions.

edit:

Regarding security, this solution is very good. The test mirror account doesn't need to have write,exec, or even read permission on the live account.

07-21-2002, 08:44 AM	#6
thelenian Member Join Date: Apr 2002 Posts: 122	The simplist approach I can think of would bypass system calls completely. Just do message passing through a file. It's sort of a kludge, but it gets the job done. All you need is a perl script running in the background that continually checks for the existance of a certain file. If the file exists, the script executes whatever checks are necessary to ensure that it's a valid boot attempt, calls the boot script., and then deletes the file. The command to reboot the MUD from the test port would simply create the file that the script checks for. This will work even if your test MUD is on a different account, as long as the script is running with the proper permissions. edit: Regarding security, this solution is very good. The test mirror account doesn't need to have write,exec, or even read permission on the live account.