**** BEGIN LOGGING AT Thu Apr 04 02:59:57 2019
Apr 04 07:04:22 <luke-jr> DocScrutinizer05: if only the boolean result matters, exit 1 works; if you need the exact correct result, then sending signal 2 won't be right for any of the other signals
Apr 04 15:25:18 <DocScrutinizer05> no, the return code does NOT matter, see the article I linked
Apr 04 15:27:07 <DocScrutinizer05> you may go fancy and set up a separate interrupt handler (trap) for every signal you catch, end send that very signal to $$ (self) after you did clanup
Apr 04 15:27:26 <DocScrutinizer05> usually this is not necessary though
Apr 04 15:30:28 * DocScrutinizer05 idly wonders if there is, or bash could learn to provide, a $SIGNAL env that contains an array of numeric IDs of signals the process received
Apr 04 15:41:27 <brolin_empey> DocScrutinizer05: Somewhat like ${PIPESTATUS} in bash?
Apr 04 15:46:36 <DocScrutinizer05> sort of
Apr 04 15:47:53 <DocScrutinizer05> of course you can do    trap 'cleanup INT' INT; trap 'cleanup ABRT' ABRT; ...
Apr 04 15:48:25 <DocScrutinizer05> and have cleanup() deal with the signame parameter
Apr 04 15:52:41 <DocScrutinizer05> or   for (i=1; i<=32; i++); do trap "cleanup $i" -$i; done;  #?
Apr 04 16:02:35 <DocScrutinizer05> I'm not sure what the latter will do
Apr 04 16:03:38 <DocScrutinizer05> not even allowed according to POSIX which only allows names for signal/condition, no integers
**** ENDING LOGGING AT Fri Apr 05 02:59:57 2019