From owner-freebsd-isdn Sat Feb 28 05:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09258 for freebsd-isdn-outgoing; Sat, 28 Feb 1998 05:41:19 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09253 for ; Sat, 28 Feb 1998 05:41:16 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.8/8.6.9) with ESMTP id OAA04026 for ; Sat, 28 Feb 1998 14:42:13 +0100 (CET) Message-Id: <199802281342.OAA04026@peedub.muc.de> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-isdn@FreeBSD.ORG Subject: Re: Still a bug in the AM Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 27 Feb 1998 19:47:11 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Feb 1998 14:42:13 +0100 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis writes: > >There seems to be a bug in the process handling code of isdnd, it happens >under FreeBSD too. > [this actually concerns problems when using isdn4bsd as an answering machine] [Hellmuth removed a little too much context] there might also be a problem with the way /bin/sh handles signals. There's been a lot of discussion on the FreeBSD-current mail list about this recently. Try using bash instead; it supposedly handles signals much better. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message