Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15297 > unrolled thread
| Started by | Steffen Nurpmeso <steffen@sdaoden.eu> |
|---|---|
| First post | 2019-08-05 15:49 +0200 |
| Last post | 2019-08-05 15:49 +0200 |
| 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.
Re: Async processes started in functions not reliably started Steffen Nurpmeso <steffen@sdaoden.eu> - 2019-08-05 15:49 +0200
| From | Steffen Nurpmeso <steffen@sdaoden.eu> |
|---|---|
| Date | 2019-08-05 15:49 +0200 |
| Subject | Re: Async processes started in functions not reliably started |
| Message-ID | <mailman.898.1565012975.1985.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web