Re: SIGINT handling

From	Bob Proulx <bob@proulx.com>
Newsgroups	gnu.bash.bug
Subject	Re: SIGINT handling
Date	2015-09-22 12:04 -0600
Message-ID	<mailman.1619.1442945094.19560.bug-bash@gnu.org> (permalink)
References	(5 earlier) <20150920161245.GA14980@chaz.gmail.com> <20150920194542.GB14980@chaz.gmail.com> <560054CE.6000208@case.edu> <20150921210755.GC5598@chaz.gmail.com> <20150922121808.GK25574@eeg.ccf.org>

Show all headers | View raw

Greg Wooledge wrote:
> Just for the record, ping is the *classic* example of an incorrectly
> written application that traps SIGINT but doesn't kill itself with
> SIGINT afterward.  (This seems to be true on multiple systems -- at
> the very least, HP-UX and Linux pings both suffer from it.)

The command I run into the problem most with is 'rsync' in a loop.

  EXIT VALUES
       0      Success
  ...
       20     Received SIGUSR1 or SIGINT

Which forces me to write such things this way.

  rsync ...
  rc=$?
  if [ $rc -eq 20 ]; then
    kill -INT $$
  fi
  if [ $rc -ne 0 ]; then
    echo "Error: failed: ..." 1>&2
    exit 1
  fi

Bob

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

Thread

Re: SIGINT handling Bob Proulx <bob@proulx.com> - 2015-09-22 12:04 -0600

csiph-web