03-01-2010
2 possibilities:
trap various signals (eg, EOF, TERM, KILL and INT) and if they occur remove the lock file
or
Write your current PID to the lock file. On start, check if the file exists and if there is a process with that PID and if it's named the same as the script. If not, run, exit otherwise.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I have an executable that takes indefinitely long time to search for the libsendfile.so in particular solaris machines only. The library is actually in the /lib folder. Where as it works fine on few of the machines, it takes long time in few others.
I have checked crle options. Its... (1 Reply)
Discussion started by: kk2202
1 Replies
2. UNIX for Dummies Questions & Answers
making a script in vi to create a shell script called wherearethey by entering the following script:
echo -n "Who are you looking for: "read userif then list=`w | grep $user | cut -c19-30` if then echo "The user $user is logged in from $list" else echo "The user $user is not logged in... (3 Replies)
Discussion started by: curtner
3 Replies
3. Shell Programming and Scripting
Now I am using the HP-UX11.11 version.
The scripts are runninh in KSH shell.
While I wan to call one executable of any Pro*C file, I have got the following error, however the executable is running fine directly.
testpri Started at 10.05.200923:40
/usr/lib/dld.sl: Bad magic number for... (0 Replies)
Discussion started by: priyankak
0 Replies
4. Shell Programming and Scripting
I need to know how to have a BASH script run every time Firefox is launched, what is the simplest way to do this? (1 Reply)
Discussion started by: glev2005
1 Replies
5. Shell Programming and Scripting
Hello everybody,
I'm unable to make my shell script an executable file.
The details are as follows:
PATH includes my $HOME/bin i.e. /rchome/rc1/bin
HOME directory is /rchome/rc1
script name is prep_mig.sh permissions set are 755
It's executing if I give below command
sh prep_mig.sh
but... (4 Replies)
Discussion started by: jitu.keshwani
4 Replies
6. Shell Programming and Scripting
Hi,
I am writing a script, and I need to incorporate some logic where I can find out the unix username of the person who is executing the script.
The issue is , a particular user could have "sesu" ed into a group id. for eg. root, and then executed the script. In that case, instead of root,... (5 Replies)
Discussion started by: neil.k
5 Replies
7. Shell Programming and Scripting
Hi group,
I am very beginner in shell scripting and self learning.
I am trying to create and executable script to run awk from user defined variables.
e.g. suppose from a given file I want to delete some rows or some columns
We need to repeat this process for many files. Thus I was... (4 Replies)
Discussion started by: smitra
4 Replies
8. Shell Programming and Scripting
Is it possible to set a nice value for an executable in a script so that every time the executable runs it has this nice value?
I'm trying to set aerender (After Effects terminal renderer) to run at +18 by replacing the original aerender script with a bash script with something like this in it: ... (3 Replies)
Discussion started by: scribling
3 Replies
9. Shell Programming and Scripting
Hi here's my code
${ORACLE_HOME}/bin/sqlplus /nolog <<!EOF
--step 5 create db script start
set feedback off
set heading off
set echo off
conn / as sysdba
spool ${ORACLE_SID}_db_link.sql
SELECT 'CREATE '||DECODE(U.NAME,'PUBLIC','public ')||'DATABASE LINK '||CHR(10)... (2 Replies)
Discussion started by: jediwannabe
2 Replies
10. Shell Programming and Scripting
Hi all,
I'm new to Unix so just wanted some help.
I've been self learning and came accross a question online that I was trying. It is to make any shell script executable, the name of the file is to be made executable.
I would use nano and type in something like
#! /bin/bash
Chmod +x... (4 Replies)
Discussion started by: HelenaR
4 Replies
KILL(1) User Commands KILL(1)
NAME
kill - send a signal to a process
SYNOPSIS
kill [options] <pid> [...]
DESCRIPTION
The default signal for kill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9, -SIGKILL or -KILL. Negative PID values may be used to choose whole
process groups; see the PGID column in ps command output. A PID of -1 is special; it indicates all processes except the kill process
itself and init.
OPTIONS
<pid> [...]
Send signal to every <pid> listed.
-<signal>
-s <signal>
--signal <signal>
Specify the signal to be sent. The signal can be specified by using name or number. The behavior of signals is explained in sig-
nal(7) manual page.
-l, --list [signal]
List signal names. This option has optional argument, which will convert signal number to signal name, or other way round.
-L, --table
List signal names in a nice table.
NOTES Your shell (command line interpreter) may have a built-in kill command. You may need to run the command described here as /bin/kill
to solve the conflict.
EXAMPLES
kill -9 -1
Kill all processes you can kill.
kill -l 11
Translate number 11 into a signal name.
kill -L
List the available signal choices in a nice table.
kill 123 543 2341 3453
Send the default signal, SIGTERM, to all those processes.
SEE ALSO
kill(2), killall(1), nice(1), pkill(1), renice(1), signal(7), skill(1)
STANDARDS
This command meets appropriate standards. The -L flag is Linux-specific.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote kill in 1999 to replace a bsdutils one that was not standards compliant. The util-linux one
might also work correctly.
REPORTING BUGS
Please send bug reports to <procps@freelists.org>
procps-ng October 2011 KILL(1)