igli 1190437381 learn If you want processes to communicate, the easiest way (besides a pipe) is to use signals. See ''help trap'' and http://wooledge.org/mywiki/ProcessManagement igli 1190439576 forget igli 1190439626 learn If you want processes to communicate, the easiest way (besides a pipe) is to use signals. See ''help trap'' | http://bash-hackers.org/wiki/doku.php?id=patch:helptexts#trap and http://wooledge.org/mywiki/ProcessManagement igli 1190439673 forget igli 1190439706 learn If you want processes to communicate, the easiest way (besides a pipe) is to use signals. See: help trap and http://wooledge.org/mywiki/ProcessManagement igli 1190440010 forget igli 1190440071 learn If you want processes to communicate, the easiest way (besides a pipe) is to use signals. See: help trap , man kill and man bash /SPECIAL PARAMETERS | http://wooledge.org/mywiki/ProcessManagement lhunath 1297674788 forget lhunath 1297674884 learn To catch and handle signals sent to bash processes, trap them: trap [command] [signal]. To do cleanup on exit, do NOT trap a bunch of signals, instead: trap cleanupFunc EXIT greycat 1319481157 forget greycat 1319481191 learn http://mywiki.wooledge.org/SignalTrap ## To clean up on exit, don't trap a bunch of signals. Instead, trap cleanupFunc EXIT