First point: you're proxying, and not redirecting.
Secondly, if the end user sees the URL change, then the ProxyPassReverse
directive is too specific. Some part of the page content could also be
causing issues, so that would need to be inspected first.
On Sat, 26 Mar 2022 at 07:53, olivier giorgi
On Sun, Mar 27, 2022 at 7:13 PM Andrew Athan
wrote:
>
>
> 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?
Thanks for the report, I opened a bug and trie
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
> In 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"
-n looks to intentionally/explicitly treat the initial file and
subsequent rotations differently, as you say abo
Sorry I hit send on this a bit too soon.
The other issue which I've confirmed is this (rotatelogs -v -e -L log -n
3 logfile 1G) output:
Rotation time interval: 0
Rotation size interval: 1073741824
Rotation time UTC offset: 0
Rotation based on localtime:
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
