Is ther anyway to inhibit the CNTRL-C key sequence from stopping a task that is being run from the command line? Thanks in advance -- Mark Hounschell dmarkh@cfl.rr.com
If you send the process to the background, it will be unaffected by CTRL+C.
Paul Miles
All Secure Networks
Visit www.allsecuredomain.com for low cost
web hosting and domain registration
----- Original Message -----
From:
Is ther anyway to inhibit the CNTRL-C key sequence from stopping a task that is being run from the command line?
Thanks in advance -- Mark Hounschell dmarkh@cfl.rr.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Have you tried capturing both standard out and standard error?
ie. mycommand > /tmp/output 2>> /tmp/output
Paul Miles
All Secure Networks
Visit www.allsecuredomain.com for low cost
web hosting and domain registration
----- Original Message -----
From:
Paul Miles wrote:
If you send the process to the background, it will be unaffected by
CTRL+C.
This particular app dies when sent to background.
-- Mark Hounschell dmarkh@cfl.rr.com
ctrl-c send SIGINT to the app. If you've written the app yourself, you can capture SININT in the initialization phase of the program (see man signal). If you haven't written the app yourself, you can always write a small wrapper that installs a custom SIGINT handler and then spawns the real app as a child. regards Anders On Friday 14 September 2001 17.57, dmarkh@cfl.rr.com wrote:
Paul Miles wrote:
If you send the process to the background, it will be unaffected by CTRL+C.
This particular app dies when sent to background.
Anders Johansson wrote:
ctrl-c send SIGINT to the app. If you've written the app yourself, you can capture SININT in the initialization phase of the program (see man signal).
If you haven't written the app yourself, you can always write a small wrapper that installs a custom SIGINT handler and then spawns the real app as a child.
regards Anders
On Friday 14 September 2001 17.57, dmarkh@cfl.rr.com wrote:
Paul Miles wrote:
If you send the process to the background, it will be unaffected by CTRL+C.
This particular app dies when sent to background.
Thank you that is what I was looking for. -- Mark Hounschell dmarkh@cfl.rr.com
On Fri, Sep 14, 2001 at 10:50:50AM -0400, dmarkh@cfl.rr.com wrote:
Is ther anyway to inhibit the CNTRL-C key sequence from stopping a task that is being run from the command line?
Thanks in advance -- Mark Hounschell
In a shell script you can use the "trap" command to implement your own signal handling. If it is a 'C' program you have the source for you can use sigset et al for your own signal handling. etc.. -- Regards Cliff
Cliff Sarginson wrote:
On Fri, Sep 14, 2001 at 10:50:50AM -0400, dmarkh@cfl.rr.com wrote:
Is ther anyway to inhibit the CNTRL-C key sequence from stopping a task that is being run from the command line?
Thanks in advance -- Mark Hounschell
In a shell script you can use the "trap" command to implement your own signal handling. If it is a 'C' program you have the source for you can use sigset et al for your own signal handling. etc..
It is one I have source for but I may or maynot be allowed to make the mod so the shell script alternative may also usefull. Thanks Mark Hounschell dmarkh@cfl.rr.com
participants (4)
-
Anders Johansson -
Cliff Sarginson -
dmarkh＠cfl.rr.com -
Paul Miles