01-18-2008
Use ps -elf to check the process & grep for u'r scripts & use kill command to kill it
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
am new to programmming
any body suggest , how to execute, shell script interactively
and like stream line edit (3 Replies)
Discussion started by: srini_ibmadmin
3 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Posting my first query in this Forum,here's my query
i want to execute 100 .sql files in unix having some code for connecting with db and executing procedures inside that,that to be run parallel like threads.want to run all the 100 .sql files simultanously.
thanks in advance. (4 Replies)
Discussion started by: santho
4 Replies
3. Shell Programming and Scripting
any idea.....
If i want to run the scripts in unix...can it be done ..just by clicking icons on a windows machine ( connectivity exists between the windows & unix machine ) (1 Reply)
Discussion started by: bishweshwar
1 Replies
4. Shell Programming and Scripting
I understand that in order to run basic unix commands I would normally type at the prompt, I would have to use the following format
system(ls -l);
or
exec(ls -l);
But when I actually try to use the command, the script fails to compile and keeps telling me there is an error with this line. ... (1 Reply)
Discussion started by: userix
1 Replies
5. Shell Programming and Scripting
Hi All,
Am using the below command to start my application using the root user
su - bin -c "/home/bin/test/start.sh"
but am getting the error becaue i have set some environment varibales in bin .profile
when i execute the command start.sh by logging directly into bin account it's... (8 Replies)
Discussion started by: ravi.sri24
8 Replies
6. Shell Programming and Scripting
Hello
I have a script that has 2 scripts that must be executed one after the other.
however, when I run the script, the 2 sub-scripts are run in parallel.
any idea how to fix this without using sleep command?
thank you (7 Replies)
Discussion started by: melanie_pfefer
7 Replies
7. Shell Programming and Scripting
Hi all,
I have set up a cron job which calls another shell script shell script which in turn calls a Java process. The cron tab looks so.
0,30 7-18 * * 1-5 /u01/home/weblogic/brp/bin/checkstatus.sh >> /u01/home/weblogic/logs/checkstatus.log
The checkstatus.sh scripts looks like this.
... (4 Replies)
Discussion started by: sirbrian
4 Replies
8. Shell Programming and Scripting
I have used ps -ef | grep <process name> to see if the process is still running or not. But, not being able to find anything in particular. Any clue on this... (4 Replies)
Discussion started by: Haimanti
4 Replies
9. Shell Programming and Scripting
I am writing a bash script to run test some scripts.
The names scripts of the scripts to tests are stored in an array.
scptArr='chcksfrd.bash'
scptArr='compute-misfit.bash'
scptArr='compute-travel-times.bash'
scptArr='create-data-tinv.bash'
scptArr='create-docs.bash' ... (3 Replies)
Discussion started by: kristinu
3 Replies
10. Shell Programming and Scripting
Hi, below is my master script wihch inturn runs 2 scripts in background
#master_script.sh
./subscript1.sh &
./subscript2.sh &
executed the master_script.sh from unix command prompt
$ ./master_script.sh
it is executing the subscripts and they are completing fine, however master_script.sh is... (2 Replies)
Discussion started by: JSKOBS
2 Replies
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 process(es) 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]
Display the name of the signal corresponding to exit_status. exit_status may be the exit status of a command killed by a signal (see
the special sh(1) parameter '?') or a signal number.
If no operand is given, display the names of all the signals.
-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.
0 Broadcast the signal to all processes in the current process group 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)
kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill argu-
ments. See csh(1) for details.
SEE ALSO
csh(1), pgrep(1), pkill(1), ps(1), kill(2), sigaction(2), signal(7)
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.
BSD
April 28, 1995 BSD