11-13-2006
The system clock sends out signals to keep everything in sync. The cpu frequency is how fast the cpu can do stuff. Your cpu frequency is 1281 Mhz and your system clock is 183 Mhz. Note that 183 * 7 = 1281. The CPU will keep its clock synced up to the system clock. All of the clocks in your system will be created by multiplying or dividing the system clock by some small integer. The cpu's all plug into a bus. And memory plugs into the same bus. This bus almost always runs at the system clock rate.
10 More Discussions You Might Find Interesting
1. Solaris
Hello Guys, :confused:
I have tried Up to my Levels
pls help me if u know any solution
Pls look out the following O/P,
Log Messages
=================================================
SUN> pwd
/usr/platform/SUNW,Sun-Fire-V240/sbin
SUN>
SUN>
SUN> prtdiag -v
bash: prtdiag: command not... (7 Replies)
Discussion started by: sure.solaris
7 Replies
2. Solaris
hi,
we have an e6900 and my sys admin says that the number of processors and memory were reduced to 4 and 8GB. However, a prtdiag |grep Memory returns 16GB of memory. So what is my system's memory? psrinfo returns 4 online and 4 offline CPUs.
Thanks.
Kumar (1 Reply)
Discussion started by: kumar27
1 Replies
3. Solaris
Hi,
Recently installed a Firmware patch on T5120 (solaris 10,138888-03).
The patch installation was Success and system came up fine as well. My apps are running fine too.
Problem is prtdiag does not work as it used to earlier. the output is very different from other t5120s I have and... (1 Reply)
Discussion started by: upengan78
1 Replies
4. Solaris
Hi, a couple of T2000 servers did not show the component status and the output was too short. There was a patch that needed to be installed. I also updated to the latest recommended patch cluster and OBP patch.
After reboot/restart of picl, it worked ok for a couple of weeks. Then suddenly it went... (12 Replies)
Discussion started by: incredible
12 Replies
5. UNIX for Advanced & Expert Users
Dear All....Help required
prtdiag -v command shows no output on my V440 server.
Following is the details:
root@sdp16b>prtdiag -v
root@sdp16b>
root@sdp16b>uname -a
SunOS sdp16b 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-V440
root@sdp16b>echo $path
/usr/sbin /usr/bin /usr/sbin... (6 Replies)
Discussion started by: Junaid
6 Replies
6. UNIX for Dummies Questions & Answers
I am having trouble figuring this one out.....Is this a 2CPU or a 4CPU v490 with 16GB? I think it is a 2CPU system, looking for confirmation.
$ prtdiag
System Configuration: Sun Microsystems sun4u Sun Fire V490
System clock frequency: 150 MHz
Memory size: 16384 Megabytes
... (1 Reply)
Discussion started by: config_boy
1 Replies
7. Solaris
Hi. I have 2 SunFire V490 servers running Solaris 10. We may have to upgrade with more memory on one of them to make it compatible with the other. Here's the one with 12GB of RAM:
Memory size: 12288 Megabytes
========================= CPUs ===============================================
... (1 Reply)
Discussion started by: th1amigo
1 Replies
8. Solaris
Hello,
I was under the impression that the Header of the prtdiag output shows the hardware vendor information in the section between System Configuration and sun4u/sun4us. But on some Solaris machines which are running on Fujitsu hardware, the vendor is shown as Sun Microsystems in this... (8 Replies)
Discussion started by: chattygk
8 Replies
9. Solaris
Hi everyone,
Please can you tell me what kind of memro we are talking about when we run :
prtdiag -v
Memory size: 98016 Megabytes
Thank you (7 Replies)
Discussion started by: adilyos
7 Replies
10. Solaris
selected lines from the output of the "prtdiag -v" command on a T5240 SUN server running Solaris 10.
Are the following known as FRU names and what do they mean?
MB/CMP0/BR0/CH0/D0
MB/CMP0/BR0/CH1/D0
SYS/FANBD0/FM0/F0
SYS/FANBD0/FM0/F1
SYS/MB/CMP0/BR1/CH0/D1 ... (1 Reply)
Discussion started by: snoman1
1 Replies
LEARN ABOUT OSX
pacemaker
PACEMAKER(8) BSD System Manager's Manual PACEMAKER(8)
NAME
pacemaker -- clock drift adjustment daemon
SYNOPSIS
pacemaker [-d drift] [-b] [-e error] [-a interval] [-i] [-v] [-n]
DESCRIPTION
pacemaker adjusts the system clock periodically to compensate for clock drift. The clock drift is normally computed by ntpd(8), which writes
a clock drift value in /var/db/ntp.drift. By default, pacemaker will call adjtime(2) once per second to slew the system clock. The daemon
is started by launchd(8) only when the drift file is present or has just been created in the file system. pacemaker detects changes in the
file and re-calculates clock adjustment values appropriately. The daemon will exit if the drift file is deleted and is not re-created within
one minute.
As a fail-safe mechanism, pacemaker will reset the system clock using settimeofday(2) if the system clock requires adjustment exceeding the
maximum value that can be accomodated by adjtime to slew the clock. In practice, this extreme case should never occur.
The -d option allows the specification of either a floating-point drift value, or the path name of an alternate drift file. If a floating
point drift value is specified, pacemaker will use the given value and will not read a drift file.
To reduce power consumption, especially when the system is using internal battery power, it may be desirable to reduce the frequency of calls
to adjust the system's clock drift. The -e and -a options, together with the -b flag allow several ways to control the clock adjustment fre-
quency.
The floating point value following -e specifies a maximum error tolerance in seconds for the system clock. For example, a value of 0.001
specifies that the clock drift adjustment should only be done frequently enough to keep the system clock error within one millisecond, based
on the current clock drift rate.
Alternatively, the clock adjustment frequency can be specified exactly as a value in seconds following -a.
When both -e error and -a interval are provided, pacemaker will choose to adjust the system clock either every interval seconds, or less fre-
quently if the clock error will remain within error seconds.
The settings for -e and/or -a may be specified for operation of the system while using an external power source, and specified independently
for operation using internal batteries. By default, the values for -e and/or -a are used for both power configurations. If the -b flag pre-
cedes -e and/or -a, then the following settings apply only when the system is using internal battery power.
For example, starting pacemaker with the following parameters will cause it to adjust the clock every 2 seconds when the system is using
external power. When running on battery power, it will adjust the clock no more than once every 10 seconds, or less frequently if the clock
error remains less than five milliseconds.
pacemaker -a 2 -b -a 10 -e 0.005
When invoked on the command-line with -i, pacemaker prints a summary of internal parameters and then exits. The -v flag causes pacemaker to
print copies of its log messages to standard error. Note that this requires running the program from the command line rather than from
launchd. -n causes pacemaker to run without actually attempting to adjust the system clock.
FILES
/var/db/ntp.drift default clock drift file
SEE ALSO
launchd(8), ntpd(8), adjtime(2), settimeofday(2).
HISTORY
The pacemaker daemon was introduced in OS X 10.9.
OS X
March 9, 2013 OS X