Date: Fri, 01 Jun 2012 09:38:38 +0400 From: Alexander Pyhalov <alp@rsu.ru> To: Jason Hellenthal <jhellenthal@dataix.net> Cc: freebsd-ports@FreeBSD.org Subject: Re: [ GSOC ] Differences in shell behaviour Message-ID: <4FC8555E.3090802@rsu.ru> In-Reply-To: <20120601035349.GA97671@DataIX.net> References: <4E946838-4F3B-421A-839E-05E1A01464AB@FreeBSD.org> <20120601035349.GA97671@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FC8555E.3090802>