Re: Async processes started in functions not reliably started

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Async processes started in functions not reliably started
Date	2019-08-05 09:00 -0400
Message-ID	<mailman.896.1565010052.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>

Show all headers | View raw

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.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: Async processes started in functions not reliably started Chet Ramey <chet.ramey@case.edu> - 2019-08-05 09:00 -0400

csiph-web