08-30-2013
System Clock running at half speed
SCO Openserver 6.0.0 had an issue with a NIC losing it's config on reboot. Netconfig would not allow "view protocol" and apparently zeroed out the existing IP info. Repaired from console. After this event, however, the system clock seems to lose 30 seconds for every RTC minute that passes. As a result, the system clock ends up way behind pretty quickly.
The man pages suggested that info about the clock and some tunables could be found in /etc/conf/pack.d/clock/ but this directory does not exist on this install, nor on the other one in our organization.
Anyone have any ideas?
Thanks,
DPanic
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hello,
I have a Supermicro server with a P4SCI mother board running Debian Sarge 3.1. This is the "dmidecode" output related to RAM info:
RAM speed information is incomplete.. "Current Speed: Unknown", is there anyway/soft to get the speed of installed RAM modules? thanks!!
Regards :)... (0 Replies)
Discussion started by: Santi
0 Replies
2. UNIX for Advanced & Expert Users
hi all,
i need to know what swap my system is running on...
Sun-Fire-880 is my system...
physical memory= 16GB (8 CPU's)
i know generally we keep swap 2 times of real memory...
i want to know what is current swap my system is running?
following is the o/p of swap -s:
Wed Mar 29 16:08:08... (4 Replies)
Discussion started by: abhijeetkul
4 Replies
3. AIX
Hello Everyone,
I have a Domino application running on AIX 5.3 that does time conversions worldwide. It uses the operating system time as a reference for the conversion. My problem is that I need the AIX OS clock to be a 12 hour clock (AM/PM) rather than a 24 hour clock. I have tried the date... (2 Replies)
Discussion started by: RTwitchell
2 Replies
4. Filesystems, Disks and Memory
I analysed disk performance with blktrace and get some data:
read:
8,3 4 2141 2.882115217 3342 Q R 195732187 + 32
8,3 4 2142 2.882116411 3342 G R 195732187 + 32
8,3 4 2144 2.882117647 3342 I R 195732187 + 32
8,3 4 2145 ... (1 Reply)
Discussion started by: W.C.C
1 Replies
5. Shell Programming and Scripting
Hi,
I currently use the ntpdate and date command to sync the internal clock source of my Solaris systems to the primary domain controller.
admin@myserver # ntpdate -d -u 192.168.???.???
14 Jan 17:42:02 ntpdate: ntpdate 3-5.93e+sun 03/06/05 23:16:45 (1.4)
transmit(192.168.???.???)... (2 Replies)
Discussion started by: jamba1
2 Replies
6. UNIX for Advanced & Expert Users
Hi, I have the problem that in the fstab indicating that the check is made of a particular filesystem during the boot process, if for any reason I have deleted, if it is to check the filesystem on boot, Linux will not start and asks password to enter maintenance mode. What I want is to keep an... (1 Reply)
Discussion started by: jailcreator
1 Replies
7. AIX
VIO Server connected to switch port and running with half duplex speed on one of the shared ethernet adapter. We have verified at switch end and everythings looks good.
Other ethernet adapter in the VIO server are connected and running in Full duplex speed.
Please help me find why this shared... (4 Replies)
Discussion started by: mugunthanvh
4 Replies
8. UNIX for Advanced & Expert Users
Hi, I've got an issue which I've been 'google-fu'ing without much luck. We have a legacy program which has been plagued by an issue for a long time and I've been tasked to investigate/fix.
The program uses XMotif2.1 (required due to dependency on an old GUI designer) and runs on a RHEL7... (4 Replies)
Discussion started by: altrefrain
4 Replies
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system
SYNOPSIS
halt [-dlnpqvxz]
poweroff [-dlnqvxz]
reboot [-dlnqvxz] [arg ...]
DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds
for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including
entering a shutdown record into the login accounting file and sending a message via syslog(3).
The options are as follows:
-d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a
corrupted or misbehaving system.
-l Suppress sending a message via syslog(3) before halting or restarting.
-n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on
fire.
-p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt.
This option is only valid for halt.
-v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2).
-x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2).
-z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2).
-q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used.
If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string
is passed to the firmware on platforms that support it.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom.
SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8)
HISTORY
A reboot command appeared in Version 6 AT&T UNIX.
The poweroff command first appeared in NetBSD 1.5.
CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically
reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib-
erate attempts to evade this.
This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis-
abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode.
BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell,
you have to exec reboot or exec halt.
BSD
February 16, 2011 BSD