Re: [exim-dev] Changes in the daemon startup code, fd's not …

Top Page
Delete this message
Reply to this message
Author: Marc Haber
Date:  
To: exim-dev
Subject: Re: [exim-dev] Changes in the daemon startup code, fd's not properly closed?
On Tue, Mar 01, 2005 at 02:53:47PM -0800, John W. Baxter wrote:
> I'm not someone experienced with the actual code, but change 4.50/75 seems
> relevant:
>
>
> 75. A backgrounded daemon closed stdin/stdout/stderr on entry; this meant
> that those file descriptors could be used for SMTP connections. If anything
> wrote to stderr (the example that came up was "warn" in embedded Perl), it
> could be sent to the SMTP client, causing chaos. The daemon now opens stdin,
> stdout, and stderr to /dev/null when it puts itself into the background.


If the processes get stuck, I can see exim's stdin, stdout, stderr
open to /dev/null just fine. The pipe to the debconf process which
prevents it from exiting ist something else.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835