07-10-2008
why not create a scriptname.PID while the script is running. At the end of the scirpt it can remove this. Then the script can check for the existing of the .PID file and exit if it exists.
thought?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to write a script to monitor user processes that revert to parent process id = 1
I can do this with a grep " 1 " or awk and evaluation.
but
Is there a switch on the ps command or another command to specify parent id on proccesses?
I tried ps with the -p ppid=nnnnn but it... (6 Replies)
Discussion started by: MizzGail
6 Replies
2. Shell Programming and Scripting
how to find the chid process id from given parent process id.... (the chid process doesnot have sub processes inturn) (3 Replies)
Discussion started by: guhas
3 Replies
3. UNIX for Dummies Questions & Answers
Suppose we have the following process tree:
init-> ProcessA->processB->processC
then I kill processB
Who is the parent of the processC?
init or the processA (6 Replies)
Discussion started by: Puntino
6 Replies
4. UNIX for Dummies Questions & Answers
hello
i am not a unix programmer but i need to solve a particular problem using unix.
suppose i have a user XYZ logged on to a system called ABC. i want to get the parent process id for the user and kill it
i am using
ps -ef | grep XYZ | grep ABC
it returns me all the processes for... (2 Replies)
Discussion started by: ajit.yadav83
2 Replies
5. UNIX for Dummies Questions & Answers
I need to kill all the processes of user "release" on system "PROterm" or the parent process for the user
I did this
ps -ef | grep PROterm | grep release
i got
release 2900014 2961494 0 12:19:44 pts/3 0:00 PROterm
release 3264694 2900014 0 12:19:44 - 0:00 PROterm
if i... (7 Replies)
Discussion started by: ajit.yadav83
7 Replies
6. Shell Programming and Scripting
Hi All,
I have two ksh script. 1st script calls the 2nd script and the second script calls an 'C' program.
I want 1st script to wait until the 'C' program completes.
I cant able to get the process id for the 'C' program (child process) to make the 1st script to wait for the second... (7 Replies)
Discussion started by: sennidurai
7 Replies
7. Shell Programming and Scripting
Hey all, I need to launch a script from within 2 other scripts that can run independently of the two parent scripts... Im having a hard time doing this, if anyone knows how please let me know.
More detail.
ScriptA (bash), ScriptB (ksh), ScriptC (bash)
ScriptA, launches ScriptB
ScirptB,... (7 Replies)
Discussion started by: trey85stang
7 Replies
8. Emergency UNIX and Linux Support
Hello, everyone.
Here's a program:
pid_t pid = fork();
if (0 == pid) // child process
{
execvp ...;
}
I send a signal (such as SIGINT) to the parent process, the child process receive the signal as well as the parent process.
However I don't want to child process to receive the... (7 Replies)
Discussion started by: jackliang
7 Replies
9. Shell Programming and Scripting
Hi everyone
i am very new to linux , working on bash shell.
I am trying to solve the given problem
1. Create a process and then create children using fork
2. Check the Status of the application for successful running.
3. Kill all the process(threads) except parent and first child... (2 Replies)
Discussion started by: vizz_k
2 Replies
10. Programming
Hi:
I have a program written in FORTRAN running on AIX platform.
It is because missing of documentation and without root password, therefore we want to modify the program so that we can find out which script/program that call this FORTRAN program.
I have google for few days, all of them are... (3 Replies)
Discussion started by: cstsang
3 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again to
run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)