[Oorexx-devel] Fwd: ApacheCon Europe Talk "Scripting Apache OpenOffice" with ooRexx ...

2012-11-09 Thread Rony G. Flatscher
Original Message Subject:ApacheCon Europe Talk "Scripting Apache OpenOffice" with ooRexx ... Date: Fri, 09 Nov 2012 16:55:10 +0100 From: Rony G. Flatscher To: RexxLA Members mailing list Hi there, just came back from this week's ApacheCon Europe 2012 conf

Re: [Oorexx-devel] Intercepting kill command

2012-11-09 Thread CVBruce
I agree with you. SIGHUP, is still under the users control. If they want the program to continue processing after a SIGHUP, they can always start the program with the "nohup" command. I think that this would be the expected behavior. Bruce Sent from an undisclosed location. On Nov 9, 2012,

Re: [Oorexx-devel] Intercepting kill command

2012-11-09 Thread David Ashley
I have been giving this some thought and I would like to discuss this further before we implement these changes. I believe there is a basic difference between the SIGTERM and SIGHUP signals and the way they should be processed. While I do not have a problem with SIGTERM being handled by the script