Mercurial > 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 | 08114f7dcc23 |
children |
line wrap: on
line source
Subject: Warning: could not yet send message From: MAILER-DAEMON@${host_name} To: ${return_path} MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="${uid}/${host_name}" This is a MIME-encapsulated message. --${uid}/${host_name} Content-Description: Notification Content-Type: text/plain This message was sent to you by the mailer daemon (${package} ${version}) at ${host_name}. Sorry, but your mail could not yet be delivered to all recipients. Delivery to the following recipients has been defered: @failed_rcpts Delivery will be tried again, until it is either successful or a timeout has been reached. If the latter happens, you will get a delivery failure notice. This error message may give you a hint about what caused the delay: ${err_msg} If you need help, write to <postmaster@${host_name}>. The headers of your message follow attached: --${uid}/${host_name} Content-Description: Undelivered Message Headers Content-Type: message/rfc822 @msg_headers --${uid}/${host_name}--