Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKQ1sVPj=KL4XTFK0dgx1EQcCxGz9OaXTYEzPijLjt7ihUKyyQ@mail.gmail.com>
References: 
 <CALK=YjMVUvaBc0KTPFBgrdM7Pygd=+ZUk_30pCq2X9UmTXYPYw@mail.gmail.com>
	<CAKQ1sVPj=KL4XTFK0dgx1EQcCxGz9OaXTYEzPijLjt7ihUKyyQ@mail.gmail.com>
Date: Fri, 12 Feb 2016 16:40:40 -0500
Message-ID: 
 <CALK=YjMRHP5ovR3ECWOFn0m=CVfK9i0EddXs6iutNpAxWvJm4A@mail.gmail.com>
Subject: Re: rotatelogs and SIGTERM?
From: Eric Covener <covener@gmail.com>
To: Apache HTTP Server Development List <dev@httpd.apache.org>
Content-Type: text/plain; charset=UTF-8

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.dev@gmail.com> wrote:
> On Fri, Feb 12, 2016 at 8:25 PM, Eric Covener <covener@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?


-- 
Eric Covener
covener@gmail.com