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


Groups > gnu.bash.bug > #15296 > unrolled thread

Re: Async processes started in functions not reliably started

Started byChet Ramey <chet.ramey@case.edu>
First post2019-08-05 09:00 -0400
Last post2019-08-05 09:00 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#15296 — Re: Async processes started in functions not reliably started

FromChet Ramey <chet.ramey@case.edu>
Date2019-08-05 09:00 -0400
SubjectRe: Async processes started in functions not reliably started
Message-ID<mailman.896.1565010052.1985.bug-bash@gnu.org>
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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web