[Pymilter] Re: Python-milter SIGHUP or restart

[Stuart D. Gathman]

On Mon, 8 Sep 2008, Jan ONDREJ (SAL) wrote:

>   I am using pymilter in my project SAGATOR. An user reported me a problem,
> that after this process receives an SIGHUP signal, process is ended and do
> now work more.
> 
>   This behaviour looks to be standard for milter and is hardcoded. I can't
> overwrite SIGHUP handler, because it's still overwritten in milter.

That is correct, libmilter takes over signal handling. 

>   But problem starts again, when I am trying to restart .runmilter().
> Next start in same process does not work. Is it a bug of python-milter or
> why this happens? An example scripts is attached to this email.

I've never seen a C milter that restarts runmilter() in the same process.

>   I am using SIGHUP to rotare log files. It's required for proper
> functionality of SAGATOR. Changing this signal may be hard or impossible,
> because there are other services, which use signals in sagator.
> 
>   I need to fix one of these problems to make my project functional again:
>     - my own SIGHUP handler
>     - ability to restart .runmilter()

-- 
	      Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.