You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make this work we should probably rethink the logrotation, so that it stores the time for the next rotation, and if that time is far future we set a timeout below the limit (less than approx 25 days) which checks whether we are ready for a logrotation or not, and if not we simply set a new timeout, either on the exact time if it is less than 25 days or below that limit.
The text was updated successfully, but these errors were encountered:
There is a problem with far future timeouts, which causes the rotation to execute immediately and then re-execute in an infinite loop.
The issue is related to nodejs/node-v0.x-archive#8656
To make this work we should probably rethink the logrotation, so that it stores the time for the next rotation, and if that time is far future we set a timeout below the limit (less than approx 25 days) which checks whether we are ready for a logrotation or not, and if not we simply set a new timeout, either on the exact time if it is less than 25 days or below that limit.
The text was updated successfully, but these errors were encountered: