Closed alvyn279 closed 6 years ago
Will make use of logrotate
Logrotate will successfully delete the logs and compress them. However, the running background processes for the server and the db cannot (should not) be restarted just for the sake of logs. Therefore, the output channel level will just repopulate completely server.log
with the complete info it had before the logrotate cleanup.
(SOLUTION) Worst case scenario we redirect first output channel of running server to > /dev/null/
/ This allows useless info from requests to not populate and eat up file system memory.
10
Create cron jobs to reset the log files in quill/ back to zero content every week or so.
Goal: Reduce size of these files on system.