Closed xyeLz closed 6 years ago
Well during the install process the quit
command seems to not be available yet. I wouldn't just kill any server when it exceeds the storage limit but maybe try to shutdown, then wait some time and if it doesn't respond, kill it.
I suppose that's an okay workaround. My concern is we just don't want them exceeding what we give them.
I suppose this can be changed to work how linux itself does, and once you hit the hard limit, it is done. I'll update the daemon to kill the process when it detects disk space being exceeded.
Will add a configuration since I know someone will complain.
I have a custom CS:GO image which downloads the game and updates it upon startup. When I deployed the server, I gave it 10GB of disk space. Upon starting the server, it began installing and updating Source. This process exceeded the 10GB and marked the server as "Stopping" but never actually stopped the server until the update process completed, which allowed almost 7GB of additional space to be downloaded. After attempting to start the server again, it did say that it couldn't start due to exceeding the disk space, but the fact that it allowed the extra disk space to be consumed is what concerns me. Perhaps it should mark it as "Killed" instead?
Here are the logs generated by the server: