From owner-freebsd-current Tue Aug 6 14:31: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C91C537B400 for ; Tue, 6 Aug 2002 14:31:00 -0700 (PDT) Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9368343E65 for ; Tue, 6 Aug 2002 14:30:59 -0700 (PDT) (envelope-from mailnull@mips.inka.de) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 17cBus-0001Uz-00; Tue, 6 Aug 2002 23:30:58 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.5/8.12.5) with ESMTP id g76KThMI085713 for ; Tue, 6 Aug 2002 22:29:43 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.5/8.12.5/Submit) id g76KTh0b085712 for freebsd-current@freebsd.org; Tue, 6 Aug 2002 22:29:43 +0200 (CEST) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: Signals/jobs weirdness? Date: Tue, 6 Aug 2002 20:29:42 +0000 (UTC) Message-ID: References: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > Something is fishy with signals/jobs. Getting suspended jobs back > into the foreground doesn't quite work. I don't have a clear picture > yet of what's wrong. What happens is that suspended jobs don't continue when resumed. They are stuck. If I just ^Z an instance of less(1) and fg it again, sending a SIGINT (^C) is a quick way to reanimate it. This doesn't work if several processes are involved, e.g. if you spawn an editor from less ('v') and suspend that editor. When you resume the job, there are three processes involved: less, sh -c $EDITOR, $EDITOR. You need to send SIGCONT from a different terminal to all of these. > -CURRENT/alpha as of August 3. Could be a system problem, could > be something in the new 2.05b release of bash. Neither /bin/tcsh nor the pdksh port are affected, so I assume this is a problem in bash-2.05b. I don't think this is related to the older su(1) problem people have mentioned. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message