[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wait unblocks before signals processed

From: Dan Douglas
Subject: Re: wait unblocks before signals processed
Date: Mon, 05 Nov 2012 18:11:08 -0600
User-agent: KMail/4.8.3 (Linux/3.4.6-pf+; KDE/4.8.3; x86_64; ; )

Hi Elliott. The behavior of wait differs depending upon whether you are in 
POSIX mode. Try this script, which I think does essentially what you're after 
(also here: https://gist.github.com/3911059 ):

#!/usr/bin/env bash

${BASH_VERSION+shopt -s lastpipe extglob}

if [[ -v .sh.version ]]; then
    builtin getconf
    function BASHPID.get {
        read -r .sh.value _ </proc/self/stat

function f {
    printf '%d: sleeping %d sec\n' "${@:1:2}" >&2
    sleep "$2"

    printf '%d: returning %d\n' "$1" "$3" >&2
    return "$3"

function main {
    typeset -i n= j= maxj=$(getconf _NPROCESSORS_ONLN)

    set -m
    trap '((j--))' CHLD

    while ((n++<30)); do
        f "$BASHPID" $(((RANDOM%5)+1)) $((RANDOM%2)) &
        ((++j >= maxj)) && POSIXLY_CORRECT= wait

    echo 'finished, waiting for remaining jobs...' >&2

main "$@"

# vim: set fenc=utf-8 ff=unix ts=4 sts=4 sw=4 ft=sh nowrap et:

The remaining issues are making it work in other shells (Bash in non-POSIX 
mode agrees with ksh, but ksh doesn't agree with POSIX), and also I can't 
think of a reasonable way to retrieve the exit statuses. The status of "wait" 
is rather useless here. Otherwise I think this is the best approach, using 
SIGCHLD and relying upon the POSIX wait behavior. See here: 

An issue to be aware of is that the trap will fire when any child exits 
including command/process substitutions or pipelines etc. If any are located 
within the main loop then monitor mode needs to be toggled off around them.
Dan Douglas

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]