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
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
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
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
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
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
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
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
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
LEARN ABOUT FREEBSD
sw_watchdog
WATCHDOG(4) BSD Kernel Interfaces Manual WATCHDOG(4)
NAME
watchdog -- hardware and software watchdog
SYNOPSIS
#include <sys/watchdog.h>
DESCRIPTION
The watchdog facility is used for controlling hardware and software watchdogs.
The device /dev/fido responds to a single ioctl(2) call, WDIOCPATPAT. It takes a single argument which represents a timeout value specified
as a power of two nanoseconds, or-ed with a flag selecting active or passive control of the watchdog.
WD_ACTIVE indicates that the watchdog will be kept from timing out from userland, for instance by the watchdogd(8) daemon. WD_PASSIVE indi-
cates that the watchdog will be kept from timing out from the kernel.
The ioctl(2) call will return success if just one of the available watchdog(9) implementations supports setting the timeout to the specified
timeout. This means that at least one watchdog is armed. If the call fails, for instance if none of watchdog(9) implementations support the
timeout length, all watchdogs are disabled and must be explicitly re-enabled.
To disable the watchdogs pass WD_TO_NEVER. If disarming the watchdog(s) failed an error is returned. The watchdog might still be armed!
RETURN VALUES
The ioctl returns zero on success and non-zero on failure.
[EOPNOTSUPP] No watchdog present in the kernel or none of the watchdogs supports the requested timeout value (timeout value other than
0).
[EOPNOTSUPP] Watchdog could not be disabled (timeout value of 0).
[EINVAL] Invalid flag combination passed.
EXAMPLES
#include <paths.h>
#include <sys/watchdog.h>
#define WDPATH "/dev/" _PATH_WATCHDOG
int wdfd = -1;
static void
wd_init(void)
{
wdfd = open(WDPATH, O_RDWR);
if (wdfd == -1)
err(1, WDPATH);
}
static void
wd_reset(u_int timeout)
{
if (ioctl(wdfd, WDIOCPATPAT, &timeout) == -1)
err(1, "WDIOCPATPAT");
}
/* in main() */
wd_init();
wd_reset(WD_ACTIVE|WD_TO_8SEC);
/* potential freeze point */
wd_reset(WD_TO_NEVER);
Enables a watchdog to recover from a potentially freezing piece of code.
options SW_WATCHDOG
in your kernel config adds a software watchdog in the kernel, dropping to KDB or panic-ing when firing.
SEE ALSO
watchdogd(8), watchdog(9)
HISTORY
The watchdog code first appeared in FreeBSD 5.1.
AUTHORS
The watchdog facility was written by Poul-Henning Kamp <phk@FreeBSD.org>. The software watchdog code and this manual page were written by
Sean Kelly <smkelly@FreeBSD.org>. Some contributions were made by Jeff Roberson <jeff@FreeBSD.org>.
BUGS
The WD_PASSIVE option has not yet been implemented.
BSD
December 21, 2009 BSD