From owner-freebsd-hackers Tue Dec 15 15:50:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15385 for freebsd-hackers-outgoing; Tue, 15 Dec 1998 15:50:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15378 for ; Tue, 15 Dec 1998 15:50:21 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id PAA10731; Tue, 15 Dec 1998 15:48:31 -0800 (PST) (envelope-from dhw) Date: Tue, 15 Dec 1998 15:48:31 -0800 (PST) From: David Wolfskill Message-Id: <199812152348.PAA10731@pau-amma.whistle.com> To: dillon@apollo.backplane.com, dnelson@emsphone.com Subject: Re: bin/8183 Cc: ambrisko@whistle.com, dhw@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199812152313.PAA60662@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 15 Dec 1998 15:13:39 -0800 (PST) >From: Matthew Dillon > ok, I've comitted a change to remove the signal mask prior to calling > exec. I'd appreciate it if Whistle could test it. I'm not sure this > is causing the problem, but it is the only thing I can think of. Preliminary results are encouraging: the "amcheck" does not fail (so far). Please note that before the inetd change of a few days ago, it took a few days for the symptoms to recur on the machine in question. Thus, we do not yet know if the problem is solved. We do know that the issue of unblocking the signals for inted seems to have taken care of the immediate symptoms, which is Definitely Good. [Matt, you may recall that breaking things is one of my specialties....] david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message