Re: ‘command … &’ creates subshell

From	Eli Schwartz <eschwartz@archlinux.org>
Newsgroups	gnu.bash.bug
Subject	Re: ‘command … &’ creates subshell
Date	2020-07-01 11:31 -0400
Message-ID	<mailman.768.1593617519.2574.bug-bash@gnu.org> (permalink)
References	(3 earlier) <7dvoi92p.dag@gnui.org> <09ea84b2-4fb1-6b05-7c0b-fe6b2ab00c6f@archlinux.org> <2643.1593599092@jinx.noi.kre.to> <pn9ffe39.dag@gnui.org> <2109d9c1-d0b9-32a4-99e1-7db06a0a6e81@archlinux.org>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 7/1/20 11:29 AM, Dmitry Alexandrov wrote:
> Robert Elz <kre@munnari.OZ.AU> wrote:
>>   | > If you need to ensure a disk executable is used,
>>   | Of course.  Why "command" otherwise?
>>
>> That doesn't actually work, "command" can run built-ins
> 
> Ah, yes, thanks for correction.
> 
>> there is actually no method ‹…› which guarantees execution of an executable from an external file, other than by using the complete path name
> 
> Well, I am not sure whether itʼs guaranteed, but the ‘exec’ as above does execute an external command in GNU Bash.

And in busybox, just like "env" it runs busybox builtin applets.


-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: ‘command … &’ creates subshell Eli Schwartz <eschwartz@archlinux.org> - 2020-07-01 11:31 -0400

csiph-web