10 More Discussions You Might Find Interesting
1. HP-UX
Whenever I tried to login as a root the following message is consecutively appearing
esmd: System Error: The EVM daemon has failed and cannot be restarted
I check the patches which and all previously installed. But those are correctly present. And I replace the evmstop and evmstart script... (0 Replies)
Discussion started by: siva3492
0 Replies
2. Shell Programming and Scripting
Say i have a simple example:
root@server # cat /root/scripts/test.sh
while sleep 5
do
echo "how are u mate" >> /root/scripts/test.log
done
root@server #
Instead of using rc.local to start or another script to check status, I would like make it as daemon, where i can do the following:
... (2 Replies)
Discussion started by: timmywong
2 Replies
3. UNIX for Advanced & Expert Users
Hello Gurus,
In solaris server, one folder say /appl/prod/usr/sendme get files those need to be processed. The script named checkFile.sh can process the each file.
This script checkFile.sh is not scheduled in crontab. But whenever file puts in sendme folder, the checkFile.sh is called and... (1 Reply)
Discussion started by: get_chandrakant
1 Replies
4. AIX
We encounted the following err msg
and then use
to fix this issue.
But before I finish the ipcrm cmd,the AIX systerm was restarted by using
.
After this,the cicscp cmd failed with the following:
I've tried execute it under debug mode,but got no useful information.
Who... (0 Replies)
Discussion started by: tiger_wen
0 Replies
5. Shell Programming and Scripting
Hi,
I have one query that is suppose if I have a script that pick up some files from source folder and put it into destination folder , and I want this script to run after every 1 hour, to make it configurable as per that I have options like crontab and nohup but when I test this script I have to... (2 Replies)
Discussion started by: nks342
2 Replies
6. Shell Programming and Scripting
Hi,
HI ,
I have a simple script that moves files from one folder to another folder, I have already done the open-ssh server settings and the script is working fine and is able to transfer the files from one folder to another but right now I myself execute this script by using my creditianls to... (3 Replies)
Discussion started by: nks342
3 Replies
7. Shell Programming and Scripting
I am trying to create a service to always run and monitor a script that has a tendency to hang, we could not find what is causing it to hang so are in the process of completely reprogramming just about everything, however, that will take upto 6 months.
So I need to create this to monitor the... (5 Replies)
Discussion started by: ukndoit
5 Replies
8. Red Hat
Hi All,
Hope this is right area to ask this question.
I have a shell script (bash) "wrapper.sh", which contains few simple shell command
which executes a "server.sh" (conatins code to execute a java server) as a daemon.
Now what I want to kill this "server.sh" so that the server should... (2 Replies)
Discussion started by: jw_amp
2 Replies
9. Shell Programming and Scripting
I have simple shell script that I run as cron job every hour of the day. I would like to make it a daemon that runs far more frequently like every 30 seconds or so, but I have never made daemon before. How can I do this?
-Sam (7 Replies)
Discussion started by: Sammy_T
7 Replies
10. UNIX for Dummies Questions & Answers
Would you run the ‘identd' daemon on UNIX servers? can you please Explain.
thanks in advance! (3 Replies)
Discussion started by: xoxouu
3 Replies
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)