The swr-run script is in charge of naming the log file and redirecting the output to the log file. I need to figure out why the swr binary can't do it's own boot logging. Although writing to stdout doesn't seem like the worst thing, maybe it can do both.
At the least I want to fix these issues:
If the mud fails to start, such as the port is already in use because the MUD is still running for some reason it shouldn't keep trying to start the mud with new log files forever. One example is when the port is already in use because the MUD is already running. Might need to figure out why it is getting in this state and how the shutdown.txt file works.
The swr-run script is in charge of naming the log file and redirecting the output to the log file. I need to figure out why the swr binary can't do it's own boot logging. Although writing to stdout doesn't seem like the worst thing, maybe it can do both.
At the least I want to fix these issues: