Got logrotate for managing the recycling of various os and userland logs, however the unbound generated logs are running somehow "wild" - as in exceeding the size constrain of the current log (as set in the logrotate conf). Also unbound logs that been rotated to pasture, pending shredding, just keep on bloating in size.

Have tried various settings in logroate but none seems to able to tame the unbound logs.

Anyone with a similar usecase who would not mind sharing some good practice for unbound logs with logrotate?

Reply via email to