Sponsored Content
Full Discussion: disabling watchdog
Operating Systems Solaris disabling watchdog Post 302236649 by DukeNuke2 on Tuesday 16th of September 2008 03:57:13 AM
Old 09-16-2008
yes you can... it is a setting in /etc/system. i don't know the right entry yet... but it should be something like:

set watchdog_disable=1

maybe one of the other guys knows the right syntax...
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

WatchDog ReInit

Wath is this ?? eeE: WatchDog ReInitMemory 6 for board 0 WARNING: eeE: Allocb failure in ReInitMemory Only renit manualy is a solution. :confused: Help me please Tnks (2 Replies)
Discussion started by: RoMaGo
2 Replies

2. SCO

Watchdog Problem In Unix Server

My Unix Server with SCO Unix ver 5, display Watchdog error which reads, Watchdog ReInitMemory 6 for board 0 Warning : eeE : Allocb failure in ReInitMemory. My server has 98 dumb terminals connected. It has 5 Hard Disks (SCSI) of 9.1 GB each and 512 MB RAM. Uses RAID level 5 After this error... (1 Reply)
Discussion started by: V.V.KUMAR
1 Replies

3. UNIX for Dummies Questions & Answers

disabling NIS

How do you disable a server, #1, from trying to use the NIS that is running on another server, #2? I would like the #1 server to just use the local etc/shadow file (3 Replies)
Discussion started by: calamine
3 Replies

4. Solaris

Watchdog for process

Hi, is there something build in solaris that can act as "watchdog". I have some process (service) running (e.g. Rhino). It can happen that if freezes totaly so I need to find this out and restart it totaly. My vision is two possibilities. 1) there is some counter running and I will... (2 Replies)
Discussion started by: freeangel
2 Replies

5. Solaris

doubt reg Hardware watchdog enabled

Hi, Please let me know what is hardware watchdog enabled which we get when the solaris host is booting .As per my knowledge its the one states that the POST is enabled. correct me if am wrong. (1 Reply)
Discussion started by: rogerben
1 Replies

6. AIX

no watchdog notification

Hi All, I am getting pages from EMS(Event Monitoring Servers) for "no watchdog notification" I just wonder what cause this and what to look in the system. this error was generated from production lpar which hosts p570 Thanks Mann (4 Replies)
Discussion started by: chubby362002
4 Replies

7. Solaris

Disabling sendmail

Hello everyone, can anyone tell me how to disable sendmail on solaris 10? I seem to have the sendmail process from hell. Did an SVCS | grep for mail and disabled the 2 processes it threw up. But something is still respawning sendmail (if I kill it manually) and it's doing the usual... (2 Replies)
Discussion started by: callmebob
2 Replies

8. Shell Programming and Scripting

Watchdog for a specific process trigger another process

Hi, I am willing to build a script that does a "ps-ef" or "top" on a specific process, and if it finds it running to start another process. Any suggestions to do this in a optimized way? Thanks! (2 Replies)
Discussion started by: liviusbr
2 Replies
WDOGCTL(8)						    BSD System Manager's Manual 						WDOGCTL(8)

NAME
wdogctl -- Watchdog timer control utility SYNOPSIS
wdogctl wdogctl -d wdogctl -e [-A] [-p seconds] timer wdogctl -k [-A] [-p seconds] timer wdogctl -t wdogctl -u [-A] [-p seconds] timer wdogctl -x [-A] [-p seconds] timer DESCRIPTION
wdogctl is used to manipulate watchdog timers. Watchdog timers provide a means of ensuring that a system continues to make progress. This is accomplished by use of a timer, provided by either hardware or software; when the timer expires, the watchdog resets the system. In this case of a hardware watchdog timer, this is accomplished by asserting the system's hardware reset signal. In the case of a software watchdog timer, this is accomplished by calling the kernel's normal reboot path. In order to prevent the system from rebooting, something must refresh the timer to prevent it from expiring. The NetBSD kernel provides three basic modes in which watchdog timers may operate: kernel tickle mode, user tickle mode, and external tickle mode. In kernel tickle mode, a timer in the kernel refreshes the watchdog timer. In user tickle mode, wdogctl runs in the background and refreshes the watchdog timer. In kernel tickle mode, progress of the kernel is ensured. In user tickle mode, the ability for user programs to run within a known period of time is ensured. Note that user tickle mode must be used with caution; on a heavily loaded system, the timer may expire accidentally, even though user programs may be making (very slow) progress. A user-mode timer is disarmed (if possible) when the device is closed, unless the timer is activated with the -x option. External-mode watchdogs are similar to user-mode watchdogs, except that the tickle must be done explicitly by a separate invocation of the program with the -t option. In the first two modes, an attempt is made to refresh the watchdog timer in one half the timer's configured period. That is, if the watchdog timer has a period of 30 seconds, a refresh attempt is made every 15 seconds. If called without arguments, wdogctl will list the timers available on the system. When arming a watchdog timer, the timer argument is the name of the timer to arm. Only one timer may be armed at a time; if an attempt is made to arm a timer when one is already armed, an error message will be displayed and no action will be taken. The options are as follows: -A When arming a timer, this flag indicates that an audible alarm is to sound when the watchdog timer expires and resets the system. If the selected timer does not support an audible alarm, this option will be silently ignored. -d This flag disarms the currently active timer. Note that not all watchdog timers can be disabled once armed. If the selected timer can not be disabled, an error message will be displayed and the timer will remain armed. -e Arm timer in external tickle mode. -k Arm timer in kernel tickle mode. -p period When arming a timer, this flag configures the timer period to period seconds. If the specified period is outside the timer's range, an error message will be displayed and no action will be taken. -t This flag tickles an external mode timer. -u Arm timer in user tickle mode. -x Arm timer in a modified user tickle mode: closing the device will not disarm the timer. FILES
/dev/watchdog -- the system monitor watchdog timer device SEE ALSO
acpiwdrt(4), evbarm/iopwdog(4), i386/elansc(4), i386/gcscpcib(4), i386/geodewdog(4), ipmi(4), itesio(4), pcweasel(4), pwdog(4), swwdog(4), x86/ichlpcib(4) HISTORY
The wdogctl command first appeared in NetBSD 1.6. AUTHORS
The wdogctl command and the NetBSD watchdog timer framework were written by Jason R. Thorpe <thorpej@zembu.com>, and contributed by Zembu Labs, Inc. BSD
August 11, 2011 BSD
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy