To prevent this happening to our future production environment and to ease system administration, I wrote an init script. If called with the “stop” argument, it will shut down every single process on all sites defined on a Cloverleaf server. If called with the “start” argument, it will start up the host server only to allow for a manually controlled boot of Cloverleaf.
I strongly suggest to add something similar to the next Cloverleaf release. Also, refining the runtime environment for the user hci to make gathering global site and process information more feasible would be a blast, too.
— EDIT:
A bug in the init script posted previously missed to shut down the lock daemon and monitor daemon for each site. The old script would only shut those down for the default site. This has been fixed and uploaded to this thread.