Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15297

Re: Async processes started in functions not reliably started

From Steffen Nurpmeso <steffen@sdaoden.eu>
Newsgroups gnu.bash.bug
Subject Re: Async processes started in functions not reliably started
Date 2019-08-05 15:49 +0200
Message-ID <mailman.898.1565012975.1985.bug-bash@gnu.org> (permalink)
References <20190803224008.dVNLU%steffen@sdaoden.eu> <20190803231715.YFelC%steffen@sdaoden.eu> <20190805120543.Bf9-U%steffen@sdaoden.eu> <e4abf389-e9f4-66eb-a6eb-ad3ea82f01c0@case.edu> <20190805134928.R-PMC%steffen@sdaoden.eu>

Show all headers | View raw


Chet Ramey wrote in <e4abf389-e9f4-66eb-a6eb-ad3ea82f01c0@case.edu>:
 |On 8/5/19 8:05 AM, Steffen Nurpmeso wrote:
 |
 |> Would be nice to have some shell support for signalling the parent
 |> that the child is now functional, a pipe(2) is much easier than
 |> going through temporary files, but of course not a bash bug.
 |
 |You could roll your own using a named pipe, but that's functionally no
 |different from using a temp file.

Thanks.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

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


Thread

Re: Async processes started in functions not reliably started Steffen Nurpmeso <steffen@sdaoden.eu> - 2019-08-05 15:49 +0200

csiph-web