From owner-freebsd-ports@FreeBSD.ORG Fri Jun 1 05:38:47 2012 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 435241065899 for ; Fri, 1 Jun 2012 05:38:47 +0000 (UTC) (envelope-from alp@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.238]) by mx1.freebsd.org (Postfix) with ESMTP id E39AA8FC16 for ; Fri, 1 Jun 2012 05:38:46 +0000 (UTC) Received: from pyhalov.cc.rsu.ru (pyhalov.cc.rsu.ru [195.208.255.102]) (Authenticated sender: alp@sfedu.ru) by mail.r61.net (MTA) with ESMTPSA id 99DC33A1705; Fri, 1 Jun 2012 09:38:38 +0400 (MSK) Message-ID: <4FC8555E.3090802@rsu.ru> Date: Fri, 01 Jun 2012 09:38:38 +0400 From: Alexander Pyhalov User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110306 Thunderbird/3.1.8 MIME-Version: 1.0 To: Jason Hellenthal References: <4E946838-4F3B-421A-839E-05E1A01464AB@FreeBSD.org> <20120601035349.GA97671@DataIX.net> In-Reply-To: <20120601035349.GA97671@DataIX.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.7 (mail.r61.net [0.0.0.0]); Fri, 01 Jun 2012 09:38:38 +0400 (MSK) Cc: freebsd-ports@FreeBSD.org Subject: Re: [ GSOC ] Differences in shell behaviour X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 05:38:47 -0000 Good morning. On 06/01/2012 07:53, Jason Hellenthal wrote: > > > On Thu, May 31, 2012 at 11:21:10PM +0400, Alexander Pronin wrote: >> The problem is: >> ### sh in 8.3 >> $ false& pid=$! >> $ >> [1] Done (1) false >> $ wait ${pid} >> wait: No such job: 4852 > > I don't see this behavior on 8.3-STABLE @r236350 i386 > --- > Console> false& pid=$! > Console> wait ${pid} > [1] Done (1) false > Console> echo $? > 1 It seems to behave differently, when you issue some additional commands or interact with shell. first case (8.3 r234443): $ false &pid=$! $ wait ${pid} [1] Done (1) false $ echo $? 1 second case (8.3 r234443): $ false & pid=$! $ # some interaction with shell [1] Done (1) false $ wait ${pid} wait: No such job: 59092 Now, on 9.0-RELEASE first case: $ false & pid=$! $ wait ${pid} [1] Done(1) false $ echo $? 1 second case: $ false & pid=$! $ # some activity [1] Done(1) false $ wait ${pid} $ echo $? 1 Do you see the difference ? Which behavior is correct? Can it be a sh bug? -- Best regards, Alexander Pyhalov, system administrator of Computer Center of Southern Federal University