Hey everyone, It looks to me like I may have stumbled over a bug, I tested this on Ubuntu 22.04 and 24.04 (2.4.58) so I realize that it is not with the latest apache version but that is what I have available right now.
Background - I'm trying to ship my logs off to a central logserver while completely bypassing local storage to reduce write stress on my local storage device (sata ssd). When setting ErrorLog '|/usr/bin/logger -p local3.err -t apache2' CustomLog '|/usr/bin/logger -t apache2 -p local3.info' combined The commands that gets run by apache are: /usr/bin/logger -p local3 err -t apache2 /usr/bin/logger -t apache2 -p local3 info Note how "local3.X" became "local3 X" rendering the command invalid. I have tried different ways of escaping and quoting local3.X to no avail. The only thing that works is leaving the log facility out of the command, rendering /usr/bin/logger -p err -t apache2 /usr/bin/logger -t apache2 -p info While this is good enough for my usecase it does seem wrong to me that a command is modified by apache2 and ends up in an invalid state as a result. Should I open a bug and if so where? Thanks, Eliyahu - אליהו --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
