Currently Stump generates/appends to a single log file and has no logic for automatically cleaning it up. There are API endpoints and other utility functions around wiping the log file, but I think it would be quite easy and less hassle to introduce rolling log. On a memory constrained machine, if someone were to set a verbose log level, this could easily OOM for a very actively used server
Currently Stump generates/appends to a single log file and has no logic for automatically cleaning it up. There are API endpoints and other utility functions around wiping the log file, but I think it would be quite easy and less hassle to introduce rolling log. On a memory constrained machine, if someone were to set a verbose log level, this could easily OOM for a very actively used server