Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 24974 invoked by uid 500); 11 Mar 2002 23:30:02 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 24917 invoked by uid 501); 11 Mar 2002 23:30:01 -0000 Date: 11 Mar 2002 23:30:01 -0000 Message-ID: <20020311233001.24916.qmail@apache.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org, From: Holger Metschulat Subject: general/5089 Reply-To: Holger Metschulat The following reply was made to PR general/5089; it has been noted by GNATS. From: Holger Metschulat To: apbugs@Apache.Org Cc: Subject: general/5089 Date: Tue, 12 Mar 2002 00:28:22 +0100 (MET) The Bug seems to be in the Linux kernel: On this machine, all processes are invoked with the ALRM signal blocked. This also makes the usage of ping or ntpdate impossible. The following lines in child_main() solved the problem: sigemptyset(&sigs); sigaddset(&sigs,SIGALRM); sigprocmask(SIG_UNBLOCK,&sigs,NULL); signal(SIGALRM, alrm_handler); The OS was: Linux linux 2.2.16 #9 SMP Tue Sep 25 17:00:24 MEST 2001 i686 unknown