Sponsored Content
Operating Systems SCO System Clock running at half speed Post 302849077 by jgt on Friday 30th of August 2013 08:47:37 PM
Old 08-30-2013
What did you do "repaired from console"?
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

dmidecode, RAM speed = "Current Speed: Unknown"

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

What swap is my system running on?

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

AIX 5.3 12 Hour System Clock

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

data from blktrace: read speed V.S. write speed

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

Sync Solaris System Clock With PDC Using Cron

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

Fsck in running system

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

Connected and Running with half duplex speed

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

Xt timer call, XtAppAddTimeout, hangs on system clock jump backwards

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
WD_KEEPALIVE(8) 					      System Manager's Manual						   WD_KEEPALIVE(8)

NAME
wd_keepalive - a simplified software watchdog daemon SYNOPSIS
wd_keepalive [-c filename|--config-file filename] DESCRIPTION
This is a simplified version of the watchdog daemon. If configured so it only opens .IR /dev/watchdog , and keeps writing to it often enough to keep the kernel from resetting, at least once per minute. Each write delays the reboot time another minute. After a minute of inactivity the watchdog hardware will cause a reset. In the case of the software watchdog the ability to reboot will depend on the state of the machines and interrupts. The wd_keepalive daemon can be stopped without causing a reboot if the device /dev/watchdog is closed correctly, unless your kernel is com- piled with the CONFIG_WATCHDOG_NOWAYOUT option enabled. Under high system load wd_keepalive might be swapped out of memory and may fail to make it back in in time. Under these circumstances the Linux kernel will reset the machine. To make sure you won't get unnecessary reboots make sure you have the variable realtime set to yes in the configuration file watchdog.conf. This adds real time support to wd_keepalive: it will lock itself into memory and there should be no problem even under the highest of loads. On system running out of memory the kernel will try to free enough memory by killing process. The wd_keepalive daemon itself is exempted from this so-called out-of-memory killer. OPTIONS
Available command line options are the following: -c config-file, --config-file config-file Use config-file as the configuration file instead of the default /etc/watchdog.conf. FILES
/dev/watchdog The watchdog device. /var/run/wd_keepalive.pid The pid file of the running wd_keepalive. SEE ALSO
watchdog.conf(5) watchdog(8) 4th Berkeley Distribution January 2005 WD_KEEPALIVE(8)
All times are GMT -4. The time now is 03:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy