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 OSF1
niffconfig
niffconfig(8) System Manager's Manual niffconfig(8)
NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF)
SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...]
OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options.
Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there
is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If
num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic
monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t
option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this
option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already
being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame-
ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the
specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor
thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num
is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout).
Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout).
DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters
that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter-
faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command.
Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified.
EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to
declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being
monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0
SEE ALSO
Daemons: niffd(8)
Information: EVM(5), nifftmt(7)
niffconfig(8)