01-08-2007
Thanks vino. But the problem with the watchdog script is it might get killed under similar circumstances; I mean when a unix server is preparing for rebooting. So, it doesn't seem useful solution.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to know how to enter a unix path in a cgi script for a guest book:
example:
My URL is http://www.kitachi.info
I have an html file in the main folder on my site, the file is called :
gbook.html
what would the correct unix path for this file be ???
the part of the script... (1 Reply)
Discussion started by: akitachi
1 Replies
2. Programming
Hi Everybody,
I have gone through man of sigwait and new to UNIX signals. Could anyone explain me about the following lines mentioned in sigwait man help ?
"The selection of a signal in set is independent of the signal
mask of the calling thread or LWP. This means a thread or
LWP can ... (1 Reply)
Discussion started by: md7ahuja
1 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I was wondering if anyone could help me here.
I have got a Unix Server (Solaris 8) which we access over the network from a Windows NT machine using Exceed. The Unix box has Samba installed so it is very easy to send a signal from Windows to UNIX by simply creating a dummy file which... (3 Replies)
Discussion started by: robbiegregg
3 Replies
4. Shell Programming and Scripting
hey champs,
I have a process running.......i have to catch/trap the signal when the process is being interupted/killed (kill -9 pid) option......
how can i achieve the same thru my process........
let my process is a.sh and it supposed to take 13 mins to complete, but due to some problem ,... (15 Replies)
Discussion started by: manas_ranjan
15 Replies
5. Programming
Hi,
when i compile my java code in UNIX using javac, the class file is getting created. But when i try to run the code using java - classpath command, i get the following error.
----------------------------------------
/u/up11/sample/request:>java -classpath /u/up11/sample/request... (0 Replies)
Discussion started by: satish2712
0 Replies
6. Shell Programming and Scripting
My data is something like shown below.
date1 date2 aaa bbbb ccccc
date3 date4 dddd eeeeeee ffffffffff ggggg hh
I want the output like this
date1date2 aaa eeeeee
I serached in the forum but didn't find the exact matching solution. Please help. (7 Replies)
Discussion started by: rdhanek
7 Replies
7. Shell Programming and Scripting
Dear All
We have JBOSS server running on Linux we need to track Graceful Shutdown(SIGTERM) and Forceful Shutdown(SIGKILL) timestamp and write it into one file, I am new to UNIX Signal processing if is it possible how to detect it?
We generally do
$kill PID For Graceful... (5 Replies)
Discussion started by: mnmonu
5 Replies
8. Solaris
I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM.
Can someone tell me what is the behavioral difference among these 3 signals in kill command?
Thanks! (2 Replies)
Discussion started by: joe228
2 Replies
9. Programming
Hi all,
Sorry about the title,at first i decided to ask a problem about the signal mechanism,however,i'm now figured it out.Sorry to forget modify the title:wall:.I had a small problem that if i use the code which is commented,the code would get a segment fault,while the above code NOT.what's... (4 Replies)
Discussion started by: homeboy
4 Replies
10. Programming
in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario:
client:Knock Knock
server:who's there
client: Eric
Server:Eric,Welcome.
client:exit
all process terminated
... (1 Reply)
Discussion started by: ouou
1 Replies
LEARN ABOUT NETBSD
wdogctl
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