You might have to observe or log a while to see. I have used a simple script to find processes that are using high CPU, where I do a ps -ef every N seconds, and compare them, suppressing lines with 0-1 second CPU used, using some sort, comm -13 and grep. Logging time for each pass is good, too, so you can see who runs what when to drive it up. You may find a looping process right off the bat. It goes something like this:
Last edited by DGPickett; 01-03-2011 at 10:21 PM..
Good morning,
I need some help figuring out what's eating up my cpu. My application can't get enough cpu to do its job. this is a sunfire V440 2CPU's at 1/593 GHZ with 8GB of memory. In the morning hours the box is at less than 3%. I can't figure out what else is using the CPU. We use foglight and... (2 Replies)
Hi am facing high cpu utilization on my sybase server.
I have P550
Number Of Processors: 4
Processor Clock Speed: 1656 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 65-D837E
Memory Size: 7840 MB
in topas it shows
Name PID CPU% PgSp Owner
dataserv 565264 ... (1 Reply)
In Production system there is 12 Non-Global Zones. So in that 12 Non-Global zones one of the Non-Global zone taking 60-70% CPU usage and load average become very high.
Running processors are 52 only.
Please advise me is there any way to reduce the CPU sharing Utilization. (Most Urgent)
... (9 Replies)
Hi All,
i have a script that finds the file with .txt .zip .Z .gzip that are 3 days old in directory /abc/def and removes them
find /abc/def -name '0*.txt' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.zip' -mtime +6 -exec rm {} \;
find /abc/def -name '0*.gzip' -mtime +6... (3 Replies)
There is a script which processes the incoming files from a particular directory and sleeps if it doesnt find any. Currently, i have been told that eventhough there are no files to process, the CPU utilization is very high. An independent evaluation by advisory specialist has found this script does... (2 Replies)
Hi,
I am working on a solaris app processor and the vsh goes high from time to time. I have executed various ps commands and switches and have found that it looks like the rlogind daemon is terminating vsh and not cleaning up after itself. There are also something like 10 zombies hanging around... (2 Replies)
Hello all,
I am very new to unix and trying to solve this problem.
I have cluster of 3 nodes. when I run TOP command on each server, I see a two GZIP processess with very high CPU utilization even,if I don't go backups or unzipping.
Can somebody tell me what is the problem, I don't want... (1 Reply)
Hi,
i am observing few processes taking high CPU and when i got some more detials about them it looks like this
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9452 xmp 25 0 16736 1224 860 R 100.0 0.0 903:54.18 ffmpeg -i -
9777 xmp 25 0 16736 1224 ... (1 Reply)
Hi Experts,
I need to understand few basic things regarding top command result from one of the node i have collected:
Cpu0 : 4.6%us, 2.0%sy, 0.0%ni, 91.4%id, 1.3%wa, 0.3%hi, 0.3%si, 0.0%st
Cpu1 : 0.0%us, 0.3%sy, 0.0%ni, 99.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : ... (5 Replies)
Hi,
Please suggest how to troubleshoot, kswapd is utilizing high cpu?
also wanted to know which parameters are important and needs to be added with sar command for monitoring the performance of Linux (Oracle 5.8 -64 bit
Please guide me.
I am facing the issue where server is getting... (0 Replies)
Discussion started by: manoj.solaris
0 Replies
LEARN ABOUT SUNOS
cron
cron(1M) System Administration Commands cron(1M)NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)