| 00:00.34 | *** join/#maemo Kilroo (~Kilroo@173.94.24.151) |
| 00:05.42 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 00:51.10 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 01:05.58 | *** join/#maemo keithzg (~keithzg@198-48-134-113.cpe.pppoe.ca) |
| 01:47.24 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 04:34.04 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 05:09.09 | *** join/#maemo chainsawbike (~chainsawb@unaffiliated/chainsawbike) |
| 06:25.17 | *** join/#maemo dafox (~dafox@188.206.102.9) |
| 06:36.10 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 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 |
| 08:34.08 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 08:35.27 | *** join/#maemo eMHa (~mh@217.5.215.150) |
| 08:37.32 | *** join/#maemo eMHa_ (~mh@217.5.215.150) |
| 09:13.25 | *** join/#maemo richrboo_ (~richrboo@94.197.121.110.threembb.co.uk) |
| 09:20.57 | *** join/#maemo jon_y (~enforcer@2001:f40:91d::61f) |
| 10:29.42 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 10:30.02 | *** join/#maemo povbot (~supybot@office.pov.lt) |
| 14:46.32 | *** join/#maemo Kabouik (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8) |
| 15:15.01 | *** join/#maemo dderby (~dderby@dynamic-186-31-169-206.dynamic.etb.net.co) |
| 15:25.18 | DocScrutinizer05 | no, the return code does NOT matter, see the article I linked |
| 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 |
| 15:27.26 | DocScrutinizer05 | usually this is not necessary though |
| 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 |
| 15:41.26 | brolin_empey | DocScrutinizer05: Somewhat like ${PIPESTATUS} in bash? |
| 15:44.21 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:46.36 | DocScrutinizer05 | sort of |
| 15:47.53 | DocScrutinizer05 | of course you can do trap 'cleanup INT' INT; trap 'cleanup ABRT' ABRT; ... |
| 15:48.25 | DocScrutinizer05 | and have cleanup() deal with the signame parameter |
| 15:52.41 | DocScrutinizer05 | or for (i=1; i<=32; i++); do trap "cleanup $i" -$i; done; #? |
| 15:57.03 | *** join/#maemo dafox (~dafox@188.206.101.152) |
| 16:02.35 | DocScrutinizer05 | I'm not sure what the latter will do |
| 16:03.38 | DocScrutinizer05 | not even allowed according to POSIX which only allows names for signal/condition, no integers |
| 17:28.28 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 17:59.22 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 18:01.48 | *** join/#maemo how900 (~Neo900@vm8.ganeti.dyne.org) |
| 18:01.48 | *** join/#maemo how900 (~Neo900@neo900/coreteam/communications/how) |
| 18:48.18 | *** join/#maemo pagurus (~user@i59F7A732.versanet.de) |
| 18:50.00 | *** join/#maemo Oksana (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 19:26.53 | *** join/#maemo Gizmokid2005 (~Gizmokid2@dedi2.gizmokid2005.com) |
| 19:39.35 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 19:40.53 | *** join/#maemo spiiroin (~spiiroin@37-219-132-115.nat.bb.dnainternet.fi) |
| 20:05.27 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 21:00.17 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:1::2) |
| 21:17.14 | *** join/#maemo troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439) |
| 23:04.17 | *** join/#maemo Kilroo (~Kilroo@173.94.24.151) |