[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SIGINT handling
From: |
Bob Proulx |
Subject: |
Re: SIGINT handling |
Date: |
Tue, 22 Sep 2015 12:04:45 -0600 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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
- Re: SIGINT handling, (continued)
- Re: SIGINT handling, Chet Ramey, 2015/09/19
- Re: SIGINT handling, Stephane Chazelas, 2015/09/20
- Re: SIGINT handling, Stephane Chazelas, 2015/09/20
- Re: SIGINT handling, Stephane Chazelas, 2015/09/20
- Re: SIGINT handling, Chet Ramey, 2015/09/21
- Re: SIGINT handling, Stephane Chazelas, 2015/09/21
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Greg Wooledge, 2015/09/22
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling,
Bob Proulx <=
- Re: SIGINT handling, Stephane Chazelas, 2015/09/22
- Re: SIGINT handling, Chet Ramey, 2015/09/24
- Re: SIGINT handling, Chet Ramey, 2015/09/24
- Re: SIGINT handling, Chet Ramey, 2015/09/23
- Re: SIGINT handling, Chet Ramey, 2015/09/23
- Re: SIGINT handling, Stephane Chazelas, 2015/09/24
- Re: SIGINT handling, Stephane Chazelas, 2015/09/24
- Re: SIGINT handling, Pádraig Brady, 2015/09/24
- Re: SIGINT handling, Stephane Chazelas, 2015/09/24
- Re: SIGINT handling, Stephane Chazelas, 2015/09/24