I recently build a source RPM for pennmush for building under the 1.8.x tree. I figured this would be an addition to add to the download area so that those others can get a head start streamlining a build under the 1.8.x tree as I the source RPM for 1.7.x to streamline building my SRPM. The binary and Source RPM was built under Mandriva 2006 using openssl 0.9.8 and MySQL 5.0.16. It uses perl under it, having modified the customize perl script. This part of the document is concerning the Mandriva installation features. The individual scripts in these directorys are not meant to be run independently. Use chkconfig and service commands to implement changes. /var/pennmush/ -- Home directory for pennmush user /var/pennmush/game/ -- Master copy of materials for creating a running game /var/pennmush/customize.pl -- Used to create a new game instance /etc/rc.d/init.d/pennmush -- Used to handle interaction of game with system. On installation the pennmush user and group were added to the system if they did not exist previously. All interaction between the pennmush software and the system are handled by the initscript materials. chkconfig for adding or removing service for pennmush on starting with the system. service for specific turning on or off of the individual games. All service materials must be run as root for implementation, however the functioning of the individual components that modify the system are implemented using the pennmush user. The service features that are provided are: service pennmush create - create a mush game that can be run service pennmush delete - remove a mush game existence service pennmush status - show current status of game(s) service pennmush start [GAME] - turn up or tear down one or all games service pennmush stop [GAME] - turn up or tear down one or all games service pennmush restart [GAME] - tear down then turn up game(s) service pennmush panic [GAME] - have game(s) panic dump and tear down service pennmush reboot [GAME] - have game(s) reload itself service pennmush reload [GAME] - have game(s) reload their configuration files Service pennmush feature materials: create - This will run the customize script for creating a new directory for a running version of the game. Once created any status call now show this game in its listing. delete - This will prompt the user for which game is to be removed from use and then delete the copy of the game. status - This will display any created games that can be running and will display its current status. start - By default the service will attempt to start all games. Failures or success will be shown, note that all ready running games will be displayed as a failure to start. As an option an individual game can be started, specification of the name the game was created under. stop - By default the service will attempt to shutdown all games. Failures or success will be shown, note that all ready shutdown games will be displayed as a failure to stop. As an option an individual game can be stopped, specification of the name the game was created under. restart - By default the service will attempt to shutdown and then start all games. Failures or success will be shown. As an option an individual game can be restarted, specification of the name the game was created under. panic - By default the service will attempt to do an emergency shutdown that will produce a panic dump of the database for the games. As an option an individual game can be specified using the name the game. reboot - By default the service will attempt to do an reboot of the running games. As an option an individual game name can be specified. reload - By default the service will attempt to do signal individual running games to reload their configurations. As an option an individual game name can be specified.