Re: ‘command … &’ creates subshell

From	Dmitry Alexandrov <dag@gnui.org>
Newsgroups	gnu.bash.bug
Subject	Re: ‘command … &’ creates subshell
Date	2020-07-01 00:43 +0300
Message-ID	<mailman.732.1593553403.2574.bug-bash@gnu.org> (permalink)
References	<pn9hipci.dag@gnui.org> <ac4a98bd-32f4-5c55-3b8f-1306e9758f54@case.edu> <7dvoi92p.dag@gnui.org> <09ea84b2-4fb1-6b05-7c0b-fe6b2ab00c6f@archlinux.org> <tuysgrgt.dag@gnui.org>

Show all headers | View raw

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

Eli Schwartz <eschwartz@archlinux.org> wrote:
> Useful replacements:

Thank you.  Yes, I have to pick up habit to post known user-level workarounds along with bugreports.

> If you need to ensure a disk executable is used,

Of course.  Why ‘command’ otherwise?

> $ "$(type -P cat)" &
> [1] 2092352
> $ ps --pid $! --ppid $!
>     PID TTY          TIME CMD
> 2092352 pts/42   00:00:00 cat

Also:

	$ (exec cat) &
	[1] 31427
	$ ps --pid $! --ppid $!
	  PID TTY          TIME CMD
	31427 pts/3    00:00:00 cat

Which, IIUC, is somewhat closer to what other shells do, though I cannot come up with any idea what practical difference it might make.

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

Thread

Re: ‘command … &’ creates subshell Dmitry Alexandrov <dag@gnui.org> - 2020-07-01 00:43 +0300

csiph-web