Would you please update the man page so the next poor slob doesn't lose
important traces when their modern container environment restarts and
their logs are lost as a result of using -n?
I'd do it myself but I don't have the tooling set up, nor do I know how
to submit patches to Apache proje
other words, rotatelogs is finding the large logfile, and then
creating logfile.1 ... but if logfile.1 already exists it's blown away.
It doesn't "continue where it left off"
A.
On 3/27/22 12:00 PM, Andrew Athan wrote:
I have a kubernetes pod that is running a command of
I have a kubernetes pod that is running a command of the form:
sh -c 'python foo.py 2>&1 | rotatelogs -e -L log -n 3 logfile 1G'
This works great. However, when the pod is deleted (e.g. kubectl delete
pod foo), kube restarts the pod.
Upon restart the log and logfile are empty!!! Instead, th