07-30-2009
If you are running Solaris 10 or newer, you can use the SMF framework to have your daemon restarted automatically.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop.
I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel.
It does not respond to... (5 Replies)
Discussion started by: finster
5 Replies
2. 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
3. Programming
We are forking a process B from process A and the process B should display the details it reads from process C(daemon process) continuously.
Let us say that the process C sents 100 packets.The process B receives all the 100 packets from the process C before it prints all details of 31... (1 Reply)
Discussion started by: cijkmysj
1 Replies
4. Shell Programming and Scripting
I have this shell script and in case the sybase process is been killed how can identify whether the process was killed or not, as the error code always returns 0.
#!/bin/sh
isql -S SERVER -U user -P pass<<TOP
select * from tableName
go
TOP
echo $? (2 Replies)
Discussion started by: dinjo_jo
2 Replies
5. Solaris
Hi all,
Currently I am using LDAP to store some network related data, When I run following script
./ns-slapd ldif2db
Execution of above script terminates displaying "Killed" on the console.
As far as I know, a process can be killed by two ways-
1. manually running " kill -9 <PID of LDAP... (1 Reply)
Discussion started by: akash_mahakode
1 Replies
6. UNIX for Dummies Questions & Answers
HI all,
I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting.
My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder.
If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a process which takes 13-15 mins for execution and its getting killed in the meantime.So can you please helpme out how to protect the process from getting killed.
Thanks in advance.
Regards,
Harika (9 Replies)
Discussion started by: harikagrp
9 Replies
8. UNIX for Dummies Questions & Answers
Hi reader,
I'm making a tool out of korn shell script that is running on a HP-UX server. But everytime i invoke the tool, it gets killed after a while (mid-process). I have tried re-running it a couple of times but each invocation ending up the same way ..
following is a snippet of the o/p... (8 Replies)
Discussion started by: clakkad
8 Replies
9. Shell Programming and Scripting
Hi,all.Well,I know someone has already asked this question before,however,It's too long before.So i post a new thread here.
Here is the issue.I have a shell script that use awk to calculate something and the script takes about 15 mins,it will use 100% CPU,and the system automatically killed the... (2 Replies)
Discussion started by: homeboy
2 Replies
10. Shell Programming and Scripting
I have two set of questions.
1) To skip killing some process automatically.
2) To kill other process and capture their log.
I have set of process, some needs to be killed gracefully and others should be skipped.
Listed are the process.
adm 1522... (1 Reply)
Discussion started by: murali1687
1 Replies
LEARN ABOUT HPUX
intrbald
intrbald(1M) intrbald(1M)
NAME
intrbald - daemon for balancing interrupts
SYNOPSIS
interval |
DESCRIPTION
Balancing interrupts is a process which distributes interrupts across the available CPUs in an optimal fashion. This action is performed
by (see intctl(1M)).
Performing frequent CPU migrations between system partitions may require you to perform periodic balancing of interrupts. This is espe-
cially true with systems that use WLM (Workload Manager), iCAP (Instant Capacity), and vPars (Virtual Partitions) products. If the fre-
quency of CPU migration is high, then balancing of interrupts should be performed more frequently.
The daemon monitors the system for imbalance in interrupt distribution. If an imbalance is detected after the specified interval executes
to balance the interrupt distribution. uses the parameters from the configuration file for balancing the interrupts. For more information
about the command, see intctl(1M) and the configuration file.
The daemon is started from the general purpose sequencer script (see rc(1M)), at run level 2 and is killed at run level 1. By default, the
daemon is not enabled. The daemon configuration file must be edited and the parameter set to in order to enable running the daemon. After
setting to for the first time, you can start the daemon manually by executing the script Otherwise, the daemon will automatically start the
next time the system is restarted.
Any actions performed by the daemon are logged in and details of interrupt migrations performed will be logged in the file
Options
recognizes the following options:
Instructs the running daemon to reexamine the configuration file
If the parameter has been updated, then the running daemon uses the new value. If the parameter is set to then the running
daemon stops executing.
The daemon checks if the system requires any balancing of interrupts
after interval seconds; the valid range is 5 seconds to seconds (see limits(5)).
This value can also be specified persistently in the configuration file by setting the parameter.
The default value is 60 seconds.
Setting this value too small can cause unnecessary interrupt migrations.
Gracefully kills the running daemon.
intrbald rc Configuration File
is the configuration file.
The following parameters can be persistently specified in this configuration file:
Specifies if the daemon should be started automatically during the system bootup process by the script. The daemon will only be started
automatically if this parameter is set to
NOTE: This value is by default. Before using the daemon, needs to be changed to in the file. Then the daemon needs to be started,
either manually by running or it will be started automatically at next boot via the script.
The daemon checks if the system requires any
interrupt balancing after this interval. The interval is specified in seconds; the valid range is 5 seconds to seconds (see lim-
its(5)). The default is 60 seconds.
Setting this value too small could cause unnecessary interrupt migrations.
RETURN VALUE
Exit values are:
Successful completion.
An error condition occurred.
WARNINGS
The command can be executed only by the superuser. This command should be used only by performance analysts for performance tuning pur-
poses. If the interrupts are not redistributed properly, a possible decrease in overall system performance can occur. Some processors can
become overloaded while other processors will not be optimally utilized.
FILES
configuration file. See the section above.
script.
start symbolic link.
kill symbolic link.
daemon log file.
SEE ALSO
intctl(1M), ioscan(1M), rc(1M), limits(5).
intrbald(1M)