masqmail-0.2
view tpl/warnmsg.tpl @ 72:ad034b57f3b2
fixed Debian bug 536060 (log files are closed after SIGHUP receival)
Explanation:
When run in daemon mode, first the log files are opened. They get
assigned to the file descriptors 3 and 4 usually. Then std{in,out,err}
are closed. When SIGHUP comes in, all open files are closes and
masqmail reexecutes itself. The new masqmail instance opens the log
files at fd 0 and 1 now, but std{in,out,err} are closed afterwards,
thus the log files are closed.
The fix is to close the log files before std{in,out,err} are closed,
in case the log files have higher fds. After std{in,out,err} were
closed, the log files get opened again, now.
See also: http://bugs.debian.org/536060
| author | meillo@marmaro.de |
|---|---|
| date | Wed, 16 Jun 2010 10:32:20 +0200 |
| parents | |
| children |
line source
1 Subject: Warning: could not yet send message
2 From: MAILER-DAEMON@${host_name}
3 To: ${return_path}
4 MIME-Version: 1.0
5 Content-Type: multipart/mixed;
6 boundary="${uid}/${host_name}"
8 This is a MIME-encapsulated message.
10 --${uid}/${host_name}
11 Content-Description: Notification
12 Content-Type: text/plain
14 This message was sent to you by the mailer daemon (${package} ${version})
15 at ${host_name}.
17 Sorry, but your mail could not yet be delivered to all recipients.
18 Delivery to the following recipients has been defered:
20 @failed_rcpts
22 Delivery will be tried again, until it is either successful or a
23 timeout has been reached. If the latter happens, you will get a
24 delivery failure notice.
27 This error message may give you a hint about what caused the
28 delay:
30 ${err_msg}
32 If you need help, write to <postmaster@${host_name}>.
34 The headers of your message follow attached:
36 --${uid}/${host_name}
37 Content-Description: Undelivered Message Headers
38 Content-Type: message/rfc822
40 @msg_headers
42 --${uid}/${host_name}--