I would like to allow only one instance of a script to run at any moment.
I've tried the following solution to count the instances but the result is always the number of running instances plus one and I can't find the problem
ps -ef | grep $0 | sed '/^$/ d' | sed '/grep/ d' | wc -l
Please... (2 Replies)
Hello,
I'm trying to write a script that checks for previous instances of the same script which may still be running (this script is scheduled to run every 30 minutes). I want to somehow use the pid from each instance to make sure the previous one isn't running before continuing with my... (5 Replies)
Sorry for all the threads. I am almost done. I ahve a bash script that is launching a diags program then copying the .html over my client. then it does the following line
/opt/firefox/firefox report.html
it launches it fines but the program waits for me to close the window or kill the script.... (2 Replies)
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
I have a parent process which will start 36 child process. This I achieved by using the 'for loop'.
In Parent.sh:-
./Child.sh <arg1> <arg2> ... &
If I execute "ps -ef | grep Child.sh", I can see 72 child processes running at the background. I mean I can see the duplicate of each process.
... (2 Replies)
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Hello to all @here,
as Iīm new to this forum, I will try to start in a easy way for my first post. Iīm not beginner in scripting, but also not a proffessional. So please keep easy, if I donīt understand your explanation at once ;) I donīt mean it in a bad way!
Here is the Problem:
There were... (2 Replies)
Hi there,
I'm trying to run a script remotely on a server in a particular directory named after hostname which already exists, my login session gets killed as soon as I run the below command. Not sure what is wrong, is there a better way to do it ?
Note: I can also use nohup command to run... (14 Replies)
Discussion started by: mbak
14 Replies
LEARN ABOUT OPENSOLARIS
hatimerun
hatimerun(1M) System Administration Commands hatimerun(1M)NAME
hatimerun - run child program under a timeout
SYNOPSIS
/usr/cluster/bin/hatimerun -t timeOutSecs [-av] [-e exitcode]
prog args
/usr/cluster/bin/hatimerun -t timeOutSecs [-v] [-e exitcode]
[-k signalname] prog args
DESCRIPTION
The hatimerun utility provides a convenient facility for timing out the execution of another child, program. It is useful when programming
in scripting languages, such as the Bourne shell. See sh(1).
The hatimerun utility runs the program prog with arguments args as a child subprocess under a timeout, and as its own process group. The
timeout is specified in seconds, by the -t timeOutSecs option. If the timeout expires, then hatimerun kills the child subprocess's process
group with a SIGKILL signal, and then exits with exit code 99.
You can run this command in the global zone or in a non-global zone. The command affects only the global or non-global zone in which you
issue the command.
OPTIONS
The following options are supported:
-a Changes the meaning of hatimerun radically: instead of killing the child when the timeout expires, the hatimerun utility sim-
ply exits, with exit code 99, leaving the child to run asynchronously.
It is illegal to supply both the -a option and the -k option.
-e Changes the exit code for the timeout case to some other value than 99.
-k Specifies what signal is used to kill the child process group. The possible signal names are the same as those recognized by
the kill(1) command. In particular, the signal name should be one of the symbolic names defined in the <signal.h> descrip-
tion. The signal name is recognized in a case-independent fashion, without the SIG prefix. It is also legal to supply a
numeric argument to the -k option, in which case that signal number is used.
It is illegal to supply both the -a option and the -k option.
-t Specifies the timeout period, in seconds.
-v Verbose output, on stderr.
EXIT STATUS
If the timeout occurs, then hatimerun exits with exit code 99 (which can be overridden to some other value using the -e option).
If the timeout does not occur but some other error is detected by the hatimerun utility (as opposed to the error being detected by the
child program), then hatimerunhatimerun exits with exit code 98.
Otherwise, hatimerun exits with the child's exit status.
The hatimerun utility catches the signal SIGTERM. It responds to the signal by killing the child as if a timeout had occurred, and then
exiting with exit code 98.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO kill(1), sh(1), attributes(5)Sun Cluster 3.2 10 Apr 2006 hatimerun(1M)