|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
--killing backround Procs spawned from the parent script with Ctrl+C trap
Post 303040402 by MadeInGermany on Monday 28th of October 2019 02:32:40 PM
10-28-2019
|
|
10 More Discussions You Might Find Interesting
1. AIX
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: (6 Replies)
Discussion started by: wtofu
6 Replies
2. UNIX for Dummies Questions & Answers
Hi everybody,
I'm having some problems wiriting a program in UNIX using the "fork" and "kill" system calls.
I have to create a C program P0, which creates 9 other processes
P1, P2, ..., P9, where P0 is the father of P1, P1 the father of P2, and so on.
All the processes contain an infinite... (0 Replies)
Discussion started by: davewilliams20
0 Replies
3. Shell Programming and Scripting
Hi all,
I have a shell script which calls other shell scripts, depending on the input.
Within a.sh, I have a command which calls b.sh (ie. ksh b.sh)
Normally, we use the exit function to terminate a shell. However, if I choose to call exit from b.sh, I will return to the parent shell who... (4 Replies)
Discussion started by: rockysfr
4 Replies
4. UNIX for Advanced & Expert Users
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 (2 Replies)
Discussion started by: arvindng
2 Replies
5. UNIX for Advanced & Expert Users
Hi all,
I am writing a script which calls other third party scripts that perform numerous actions. I have no control over these scripts.
My problem is, one of these scripts seems to execute and do what it is meant to do, but my calling / parent script always exits at that point. I need to... (4 Replies)
Discussion started by: mark007
4 Replies
6. Shell Programming and Scripting
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... (2 Replies)
Discussion started by: Pmarcoen
2 Replies
7. Shell Programming and Scripting
Hello,
I have a script which copies via scp several large files to a remote server. What I want is that even if someone hits CTRL-C, the scp commands continues till the end.
Here is what I wrote
#! /bin/bash
function testFunction
{
echo "COPY START"
scp large.tar.gz... (11 Replies)
Discussion started by: RobertFord
11 Replies
8. Shell Programming and Scripting
I am needing to call sqlplus and sqlldr in the same korn shell script. Below are the steps that I need to accomplish. I am new to Oracle shell scripting so an example would be great.
CBOB_LOAD.KSH - script name
Calls Oracle stored procedure sp_CBOB_CLEAR_LN_STAGING (SERVER: TESTSVR100)
Calls... (0 Replies)
Discussion started by: acewilli
0 Replies
9. Shell Programming and Scripting
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... (2 Replies)
Discussion started by: chatguy
2 Replies
10. Shell Programming and Scripting
Hi,
Just wonder if there is a way to identify the PID of the killing process using trap.
Please let me know possible solution.
#!/bin/ksh
hello () {
print "in hello";
print "PID of process issued SIGNAL"; --> this is what i'm looking for.
}
trap hello SIGKILL SIGTERM
while... (3 Replies)
Discussion started by: Gajendra_PH
3 Replies
LEARN ABOUT OSX
kill
KILL(1) BSD General Commands Manual KILL(1) NAME
kill -- terminate or signal a process SYNOPSIS
kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operand(s). Only the super-user may send signals to other users' processes. The options are as follows: -s signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -l [exit_status] If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status. -signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -signal_number A non-negative decimal integer, specifying the signal to be sent instead of the default TERM. The following pids have special meanings: -1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user. Some of the more commonly used signals: 1 HUP (hang up) 2 INT (interrupt) 3 QUIT (quit) 6 ABRT (abort) 9 KILL (non-catchable, non-ignorable kill) 14 ALRM (alarm clock) 15 TERM (software termination signal) Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page. SEE ALSO
builtin(1), csh(1), killall(1), ps(1), kill(2), sigaction(2) STANDARDS
The kill function is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible. HISTORY
A kill command appeared in Version 6 AT&T UNIX. BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided. BSD
April 28, 1995 BSD