01-17-2008
Quote:
but certain scripts which are expected to take a long time to let them go?
How to categorize them actually ?
To be on the safer side for these kind of problems; a safe and reliable approach would be to,
if possible make the process which needs to be monitored dump some [DEBUG] messages, [INFO] messages every 'n' time slice to an unique log file
With that it would be quite easy to track the status of the process by parsing the log file that is specific to each of the process that needs to be monitored.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm looking for some help, please!
I'm trying to kill any idle user processes over 40 Minutes.
I have tried putting TMOUT=2400
within the users .profile
However this does not seem to be working.
We run aix 4.3.3
with ORACLE 7.3
The above works o.k. when the user is only within the... (3 Replies)
Discussion started by: annette
3 Replies
2. Shell Programming and Scripting
I have a small problem. It's annoying though. I wrote this shell script:
#
# This script will accept two arguments. The first is a flag and the
# second is a time interval. The only valid flag is '-t' which means
# the user will specify the interval in seconds, otherwise the
# default is 600... (3 Replies)
Discussion started by: el_toro
3 Replies
3. Solaris
how can I kill all the processes belonging to an user.
I need it because I can't see a process initiated by a user and thus unable to kill it. (2 Replies)
Discussion started by: krishan
2 Replies
4. UNIX for Dummies Questions & Answers
Hi everybody,
I'm having some problems wiriting a program in UNIX using the "fork" and "kill" system calls.
I have to create a C program P0, which creates 9 other processes
P1, P2, ..., P9, where P0 is the father of P1, P1 the father of P2, and so on.
All the processes contain an infinite... (0 Replies)
Discussion started by: davewilliams20
0 Replies
5. Shell Programming and Scripting
Hi everybody!!
I've got a problem. I have a loop like this:
while true; do
some_work
sleep 10m
done
It's possible to kill the main loop process and kill all childs from it? I want to kill main process and kill the sleep also. I tried kill -9 <loop_pid> with no result
... (4 Replies)
Discussion started by: victorin
4 Replies
6. Shell Programming and Scripting
Is there a way I can run a command that will run in the kernel or in the memory and automatically kill certain scripts if they get to <defunct> processes, without having to be monitoring the server manually?
I have a Perl script which runs for 20k members and normally does not have any problems,... (2 Replies)
Discussion started by: ukndoit
2 Replies
7. UNIX for Advanced & Expert Users
Hi,
Is there a way I can kill all the child processes of a process, given its process id.
Many thanks in advance.
J. (1 Reply)
Discussion started by: superuser84
1 Replies
8. HP-UX
Hi,
Hoping someone may be able to help with some general guidance. Hope I've posted this in the right forum!
I hava DEC Workstation running OSF/1. It's will run for a period of time then slow down to the point it becomes unusable. Then i have to reboot and the whole thing repeats. I... (1 Reply)
Discussion started by: emeak
1 Replies
9. Shell Programming and Scripting
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)
Discussion started by: sukerman
0 Replies
10. Shell Programming and Scripting
i am new to unix..i have requirement to kill informatica server process.
when i used the below query
pidoff "pmserver"
it displayed 3 process running..
i need to get the 3 process and kill individual process in shell script.
Can you please assit me in this. (2 Replies)
Discussion started by: hkoshekay
2 Replies
LEARN ABOUT HPUX
cmvxserviced
cmvxserviced(1m) cmvxserviced(1m)
NAME
cmvxserviced - monitor VxVM and CVM volumes for a high availability package.
SYNOPSIS
cmvxserviced [-h|-v] [-O log_file] [-D log_level] [-t poll_interval] volume_path...
DESCRIPTION
cmvxserviced monitors VxVM and CVM volumes. It runs as a service within a package that depends on the monitored storage. When a monitored
volume fails or becomes inaccessible (see Scope of Monitoring), the service will exit, causing the package to fail on the current node.
The package's failover behavior depends on its configured settings.
cmvxserviced periodically probes each volume named by volume_path, which must identify a block device file.
Scope of Monitoring
The VxVM Volume Monitor detects the following failures:
o Failure of the last link to a storage device or set of devices critical to volume operation
o Failure of a storage device or set of devices critical to volume operation
o An unexpected detachment or disablement of a volume
The VxVM Volume Monitor does not detect the following failures:
o Failure of a redundant link to a storage device or set of devices if a functioning link remains
o Failure of a mirrored plex within a volume (assuming at least one plex is functional)
o Corruption of data on a volume which VxVM or CVM regards as enabled and active
Options
cmvxserviced supports the following options:
-h Displays the usage, as listed above, and exits.
-v Displays the monitor version and exits.
NOTE Do not include the -h or -v parameters in your service command; this will result in immediate package failure
at runtime.
-O log_file Specifies a file for logging (log messages are printed to the console by default).
-D log_level Specifies the log level. The level of detail logged is directly proportional to the numerical value of the log
level. That is, a log level of 7 will provide the greatest amount of log information. The default log level is 0.
-t poll_interval Specifies the interval between volume probes.
You can specify a polling interval of as little as 1 (one second), but bear in mind that a short polling interval
(less than 10 seconds) may impair system performance if you are monitoring a large number of volumes. HP recom-
mends a polling interval of at least 10 seconds if 50 or more volumes are being monitored by a single service com-
mand.
The default polling interval is 60 seconds.
EXAMPLES
/usr/sbin/cmvxserviced -O /pkg1/monlog.log -D 3 /dev/vx/dsk/cvm_dg0/lvol2
This command monitors a single volume, /dev/vx/dsk/cvm_dg0/lvol2, at log level 3, with a polling interval of 60 seconds, and prints all log
messages to the file /pkg1/monlog.log.
There should be a one to one relationship between monitoring services and log files. This provides a means to correlate log messages with
the originating monitor.
/usr/sbin/cmvxserviced /dev/vx/dsk/cvm_dg0/lvol1 dev/vx/dsk/cvm_dg0/lvol2
This command monitors two volumes at the default log level of 0, with a polling interval of 60 seconds, and prints all log messages to the
console.
/usr/sbin/cmvxserviced -t 10 /dev/vx/dsk/cvm_dg2/lvol3
This command monitors a single volume at log level 0, with a polling interval of 10 seconds, and prints all log messages to the console.
AUTHOR
cmvxserviced was developed by HP.
Requires Optional Serviceguard Software cmvxserviced(1m)