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

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

Re: Async processes started in functions not reliably started

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 Steffen Nurpmeso <steffen@sdaoden.eu> - 2019-08-05 14:05 +0200

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

Hi, and a nice Monday, if possible.

Steffen Nurpmeso wrote in <20190803231715.YFelC%steffen@sdaoden.eu>:
 |Steffen Nurpmeso wrote in <20190803224008.dVNLU%steffen@sdaoden.eu>:
 |  ...
 ||wanted to add a reaper process which automatically kills tests
 ||which need longer than X seconds.  That turns out to be more
 | ..
 |Seems to work[.]
 ...
 |   i=${!}
 |
 |   sleep 1
 |   if kill -USR1 ${i} >/dev/null 2>&1; then

Nonsense.  I will synchronize on a temporary file so that the
child will not die due to a not yet installed trap handler when
the first signal is emitted.
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.
Sorry for the noise.

--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)

[toc] | [standalone]

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

csiph-web