11-08-2011
The code you provided above probably has a typo in testing for the file existence. So, I removed one pipe symbol and then used the code you mentioned. It did not log any message on to the screen and just exited when I ran the script. But the DAT file was present at that time.
Just an FYI, the dat file is created every time the process runs.
So, I am still getting the error.
Any other change that I can test?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there any build in command in unix to kill all the child process for a given process ID ? If any one has script or command, please let me know.
Thanks
Sanjay (4 Replies)
Discussion started by: sanjay92
4 Replies
2. Shell Programming and Scripting
Hi there, i wonder if anyone can help
is there any way that i can write a script that will kill all current ftp processes, for example if ps -ef | grep ftp produces 3 active proceses, then I would like to somehow extract the PID for each one and pass that to kill -9
has anybody done this... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
3. Shell Programming and Scripting
Hi All,
In my project i have two process runs in the back end.
Once i start my project, and execute the command ps, i get below output:
PID TTY TIME CMD
9086 pts/1 0:00 ksh
9241 pts/1 0:02 java
9240 pts/1 0:00 shell_script_bg
java with 9241 PID is the main... (4 Replies)
Discussion started by: rkrgarlapati
4 Replies
4. UNIX for Advanced & Expert Users
Hellow Experts
i have one problem.
i run one script in backgroun.
and i want to kill that script with only script name.....
so what's the solution..
for your info
my script name is "testscript" n it contains "sleep 100"
thanks.... (16 Replies)
Discussion started by: luckypower
16 Replies
5. Shell Programming and Scripting
#!/bin/sh
who
echo "\r"
echo Enter the terminal ID of the user in use:
echo "\r"
read TERM_ID
echo "\r"
ps -t $TERM_ID | grep sh
echo "\r"
echo Enter the process number to end:
echo "\r"
read PID
echo "\r"
kill -9 $PID
What this code does is ultimately grab the PID of a users sh... (6 Replies)
Discussion started by: psytropic
6 Replies
6. Shell Programming and Scripting
I would want to run a code for 1 min and if it doesnt succeed in 1 min..I would want to exit it..I am using the following code...But the script is not going into my code part.It is waiting for 60 secs and then getting killed.
The code which is in the while loop actually takes less than 60 secs...... (6 Replies)
Discussion started by: infernalhell
6 Replies
7. Shell Programming and Scripting
Hi,
I'm trying to write a script where i'm trying to grep the PID and the associated file and list them. Then execute the KILL command sequentially on the listed PID's for ".tra" files
====================================================
ps -aux | grep mine
adm 27739 0.2 0.8 1131588... (12 Replies)
Discussion started by: murali1687
12 Replies
8. Shell Programming and Scripting
Hi,
I simply want to kill a running process using a script that read pid from a file and tries to kill it .Getting error as shown below code..
cat $HOME/BackupScript.ksh.run | head -1 | while read pid
do
ps -p $pid > /dev/null 2>&1
if ; then
kill -9 $pid
else
echo "no running $pid... (5 Replies)
Discussion started by: dhirajdsharma
5 Replies
9. AIX
I created a program to kill long running pid processes.
I am getting the following error message:
-f command cannot be found.
I also want to count the number of pids that are killed and append the results to a text file. I am new to shell script programming.
1.The first part of code... (10 Replies)
Discussion started by: dellanicholson
10 Replies
10. Shell Programming and Scripting
Hi All, Looking for a quick LINUX shell script which can continuously monitors the flle size, report the process which is creating a file greater than certain limit and also kill that process. Can someone please help me on this? (4 Replies)
Discussion started by: vasavimacherla
4 Replies
LEARN ABOUT DEBIAN
svscan
svscan(8) System Manager's Manual svscan(8)
NAME
svscan - starts and monitors a collection of services
SYNOPSIS
svscan [ directory ]
DESCRIPTION
svscan starts one supervise(8) process for each subdirectory of the current directory, up to a limit of 1000 subdirectories. svscan skips
subdirectory names starting with dots. supervise(8) must be in svscan's path.
svscan optionally starts a pair of supervise(8) processes, one for a subdirectory s, one for s/log, with a pipe between them. It does this
if the name s is at most 255 bytes long and s/log exists. (In versions 0.70 and below, it does this if s is sticky.) svscan needs two free
descriptors for each pipe.
Every five seconds, svscan checks for subdirectories again. If it sees a new subdirectory, it starts a new supervise(8) process. If it sees
an old subdirectory where a supervise(8) process has exited, it restarts the supervise(8) process. In the log case it reuses the same pipe
so that no data is lost.
svscan is designed to run forever. If it has trouble creating a pipe or running supervise(8), it prints a message to stderr; it will try
again five seconds later.
If svscan is given a command-line argument directory, it switches to that directory when it starts.
SEE ALSO
supervise(8), svc(8), svok(8), svstat(8), svscanboot(8), readproctitle(8), fghack(8), pgrphack(8), multilog(8), tai64n(8), tai64nlocal(8),
setuidgid(8), envuidgid(8), envdir(8), softlimit(8), setlock(8)
http://cr.yp.to/daemontools.html
svscan(8)