On Fri, Feb 12, 2016 at 4:46 PM, Yann Ylavic <ylavic....@gmail.com> wrote: > IIRC, solaris is doing things like that. > But here the shell would ignore SIGTERM (the trap may even be > superfluous since shells usually ignore it implicitly), so it > shouldn't be stopped by the signal and hence the message shouldn't > show up... > > On Fri, Feb 12, 2016 at 10:40 PM, Eric Covener <cove...@gmail.com> wrote: >> I lost a sentence somewhere. On one platform I use, the default for >> SIGTERM writes a message to stderr. >> >> On Fri, Feb 12, 2016 at 4:37 PM, Yann Ylavic <ylavic....@gmail.com> wrote: >>> On Fri, Feb 12, 2016 at 8:25 PM, Eric Covener <cove...@gmail.com> wrote: >>>> Recall that 2.2 ran piped loggers under a shell until somewhat late in >>>> life, and 2.4 runs them directly [by default]. >>>> >>>> rotatelogs currently doesn't do anything to block sigterm. The >>>> default ahndler for sigterm writes a short message to stderr, which is >>>> the only reason I noticed. >>> >>> Maybe you could wrap rotatelogs in a script like: >>> >>> #!/bin/sh >>> trap '' TERM >>> /path/to/real/rotatelogs $@ >>> >>> and then use: >>> ErrorLog |$/path/to/my/rotatelogs.sh ... >>> >>> in httpd.conf?
Moreso trying to flush out if it's a good or bad idea, seems simple enough to add to rotatelogs rather than requiring the wrapper.
