On Thu, Jul 31, 2025 at 2:46 PM Curry, Alan <pacu...@tsc.k12.in.us> wrote: > > On 7/31/2025 3:11 AM, E.S. Rosenberg wrote: > >> > >> 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 > > logger removes the dot from the argument while parsing it. > > <https://github.com/util-linux/util-linux/blob/stable/v2.41/misc-utils/logger.c#L997> > > That affects what ps shows. Run the same logger command from a plain old > shell and it'll look the same in ps. > That is ... unexpected, but yes that is what happens, confirmed here.
I also confirmed that when apache uses the piped output, syslog gets the full correct "local3.info" priority. Eliyahu, did you check the end effect, i.e. what facility.priority is logged (and disregard ps output)? So it is a strange decision from util-linux package to doctor its cmdline in such a way, but in the end it is only a cosmetic issue. Kalin. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
