Your message dated Wed, 16 Apr 2008 17:40:43 -0400
with message-id <[EMAIL PROTECTED]>
and subject line exim has been removed from Debian, closing #222068
has caused the Debian Bug report #222068,
regarding exim: application bug: exim(429) has SIGCHLD set to SIG_IGN but calls 
wait().
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
222068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222068
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: exim
Version: 3.35-1woody2
Severity: important
Tags: patch

Exim produces a lot of messages. I.e.:

Nov 25 13:35:12 szafir kernel: application bug: exim(24490) has SIGCHLD set to SIG_IGN but calls wa
it().
Nov 25 13:35:13 szafir kernel: (see the NOTES section of 'man 2 wait'). Workaround activated. Nov 25 13:36:15 szafir kernel: application bug: exim(25506) has SIGCHLD set to SIG_IGN but calls wa
it().
Nov 25 13:36:15 szafir kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.

This is because exim sets SIG_IGN on SIGCHLD signal and this is error for Linux kernel.

The attached patch tries to fix the bug.

See also:

http://www.exim.org/pipermail/exim-users/Week-of-Mon-20030414/052632.html


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux granat 2.4.22pre1-redhat-4.0.1.el-pentiumiii-smp #1 SMP Tue Nov 18 12:37:43 CET 2003 i686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL

Versions of packages exim depends on:
ii cron 3.0pl1-72 management of regular background p ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an ii libdb2 2:2.7.7.0-7 The Berkeley database routines (ru ii libident 0.22-2 simple RFC1413 client library - ru
ii  libldap2                     2.0.23-6.3  OpenLDAP libraries.
ii libpam0g 0.72-35 Pluggable Authentication Modules l ii libpcre3 3.4-1.1 Philip Hazel's Perl Compatible Reg

--
Piotr Roszatycki, Netia Telekom S.A.                    .''`.
mailto:[EMAIL PROTECTED]                   : :' :
mailto:[EMAIL PROTECTED]                               `. `'
                                                         `-
--- exim-3.35.orig/src/daemon.c
+++ exim-3.35/src/daemon.c
@@ -274,7 +274,9 @@
   want to wait for them as they are doing independent deliveries. */
 
   for (i = 0; i < listen_socket_count; i++) close(listen_sockets[i]);
+#ifdef CAN_IGNORE_SIGCHLD
   signal(SIGCHLD, SIG_IGN);
+#endif
 
   /* Attempt to get an id from the sending machine via the RFC 1413
   protocol. We do this in the sub-process in order not to hold up the
--- exim-3.35.orig/src/exim.c
+++ exim-3.35/src/exim.c
@@ -3141,7 +3186,9 @@
 in the non-synchronous delivery case. However, it seems that on some OS, this
 doesn't work, so the loop below contains a waitpid() just in case. */
 
+#ifdef CAN_IGNORE_SIGCHLD
 if (!synchronous_delivery) signal(SIGCHLD, SIG_IGN);
+#endif
 
 /* Save the current store pool point, for resetting at the start of
 each message, and save the real sender address, if any. */
--- exim-3.35.orig/src/smtp_in.c
+++ exim-3.35/src/smtp_in.c
@@ -3497,7 +3496,9 @@
       forking. It should be set that way anyway for external incoming SMTP,
       but we save and restore to be tidy. */
 
+#ifdef CAN_IGNORE_SIGCHLD
       oldsignal = signal(SIGCHLD, SIG_IGN);
+#endif
 
       if ((pid = fork()) == 0)
         {
@@ -3520,7 +3521,9 @@
         _exit(EXIT_FAILURE);         /* paranoia */
         }
 
+#ifdef CAN_IGNORE_SIGCHLD
       signal(SIGCHLD, oldsignal);    /* restore */
+#endif
       }
 
     if (pid < 0)

--- End Message ---
--- Begin Message ---
Version: 3.36-18.2+rm

The exim package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.

For more information about this package's removal, read
http://bugs.debian.org/420191 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.
Barry deFreese


--- End Message ---

Reply via email to