Trap CTRL-C and background process Post: 302415319

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

capture the process id when starting a background process

Hello all, How do I start a background process and save the process id to a file on my system. For example %wait 5 & will execute and print the process id. I can't figure out how to get it to a file. I've tried: > filename 0>filename 1>filename. Any assistance is most appreciated. Thanks, Jim...

2. UNIX for Dummies Questions & Answers

problems with ctrl-z, to switch foreground, background

my shell is /sbin/sh. i added stty susp '^Z' with the intention of being able to switch between foreground and background. but the result was strange. i had 2 servers. one is sun the os is 8 and the other is hpux v11. both of them had the same shell. but on hpux, it works perfectly fine while...

3. AIX

Disable ctrl-c,ctrl-d,ctrl-d in ksh script

I wrote a ksh script for Helpdesk. I need to know how to disable ctrl-c,ctrl-z,ctrl-d..... so that helpdesk would not be able to get to system prompt :confused:

4. UNIX for Advanced & Expert Users

trap ctrl c in shell script

how to trap the ctrl c in unix shell script my script is running in while loop it should not be terminate with ctrl c. if i press ctrl c while running script it shloud ignore the same. please healp.......... thanks in advance

5. Shell Programming and Scripting

trap CTRL-C problem

I am trying to trap CTRL-C, now the program I call has it's own exit message, I think this is the problem .. This is what I have now : function dothis { echo 'you hit control-c' exit } function settrap { trap dothis SIGINT } settrap until false; do ./ITGRecv.exe doneDoing this I...

6. UNIX for Dummies Questions & Answers

Script to start background process and then kill process

What I need to learn is how to use a script that launches background processes, and then kills those processes as needed. The script successfully launches the script. But how do I check to see if the job exists before I kill it? I know my problem is mostly failure to understand parameter...

7. Shell Programming and Scripting

Help with getting a Ctrl-C trap working w/ a piped tail -f...

Hi All, Although each line below seems to work by itself, I've been having trouble getting the Control-C trap working when I add the "|perl -pe..." to the end of the tail -f line, below. (That |perl -pe statement basically just adds color to highlight the word "ERROR" while tailing a log...

8. Shell Programming and Scripting

How to put FTP process as a background process/job in perl?

Hi, I am using net::ftp for transferring files now i am trying in the same Linux server as a result ftp is very fast but if the server is other location (remote) then the file transferred will be time consuming. So i want try putting FTP part as a background process. I am unaware how to do...

9. Shell Programming and Scripting

Make background process interact with fg process

Hi, I have written a menu driven shell script in which as per the choice, I run the another script on background. For eg: 1. get info 2)process info 3)modify info All the operations have different scripts which i schedule in background using &. However I wish to display the error...

10. Shell Programming and Scripting

--killing backround Procs spawned from the parent script with Ctrl+C trap

Hello: Am trying to understand why the method #2 works but method #1 does not. For both methods, sending CTRL+C should kill both the Parent script & all of the spanwd background procs. Method #1: ========================== #!/bin/sh ctrl_c() { echo "** Trapped CTRL-C" ...

LEARN ABOUT CENTOS

bashbug

BASHBUG(1)						      General Commands Manual							BASHBUG(1)

NAME

       bashbug - report a bug in bash

SYNOPSIS

       bashbug [--version] [--help] [email-address]

DESCRIPTION

       bashbug	is  a shell script to help the user compose and mail bug reports concerning bash in a standard format.	bashbug invokes the editor
       specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill  in  the  appropriate
       fields  and  exit  the  editor.	 bashbug  then	mails the completed report to bug-bash@gnu.org, or email-address.  If the report cannot be
       mailed, it is saved in the file dead.bashbug in the invoking user's home directory.

       The bug report format outline consists of several sections.  The first section provides information about the  machine,	operating  system,
       the  bash  version, and the compilation environment.  The second section should be filled in with a description of the bug.  The third sec-
       tion should be a description of how to reproduce the bug.  The optional fourth section is for a proposed fix.  Fixes are encouraged.

ENVIRONMENT

       bashbug will utilize the following environment variables if they exist:

       EDITOR Specifies the preferred editor. If EDITOR is not set, bashbug defaults to emacs.

       HOME   Directory in which the failed bug report is saved if the mail fails.

       TMPDIR Directory in which to create temporary files and directories.

SEE ALSO

       bash(1)

AUTHORS

       Brian Fox, Free Software Foundation
       bfox@gnu.org

       Chet Ramey, Case Western Reserve University
       chet@po.cwru.edu

GNU Bash-4.0							   1998 July 30 							BASHBUG(1)

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

capture the process id when starting a background process

Discussion started by: jleavitt

2. UNIX for Dummies Questions & Answers

problems with ctrl-z, to switch foreground, background

Discussion started by: yls177

3. AIX

Disable ctrl-c,ctrl-d,ctrl-d in ksh script

Discussion started by: wtofu

4. UNIX for Advanced & Expert Users

trap ctrl c in shell script

Discussion started by: arvindng