Hi how do you compare it in ksh
ALINES=$(cat AFILE | wc -l)
BFIRST=$(head -1 BFILE)
I got ALINES=9 and BFRIST=records'9'
I want 9=9 , how do you write BLINES=9 from records'9' so I can say
ALINES==BLINES
Thanks (4 Replies)
I want a soultion to compare two arrays in sh with an easy way.I want a solution to synchrose users between different AIX servers where no NIS is available. All users are meant to be same on all 10 servers. So the approach is to consider first server as master user repository and whatever the users... (0 Replies)
Hi all,
How to check whether the given the two dates is minimal.
example:
Date 1 : 23-03-2008 with timestamp
Date 2: 20-03-2008 With tmestamp
I want to compare the twodates and which it gives the minimum date
i wnat to get the output like this below
output: the Date2 is... (1 Reply)
grep '^.......$' /usr/dict/words | cut -c1,2,3,5,6,7
This gives a list of 6 character strings, some are words some not. Any suggestions on how I can get rid of the ones that aren't words and print the ones that are? I have tried look with no luck yet. (1 Reply)
I have four files, I need to compare these files together.
As such i know "sdiff and comm" commands but these commands compare 2 files together. If I use sdiff command then i have to compare each file with other which will increase the codes.
Please suggest if you know some commands whcih can... (6 Replies)
Hi,
file contains only one row.
END OF FILE. ROW COUNT: 8,9
We need to check the file contains exact string "END OF FILE. ROW COUNT: " if yes, get the 8,9 values
then compare if both are equal print the "equal" if not "notequal".
Thanks, (4 Replies)
Hi,
I need your help with the below mentioned issue:
I have 2 files say,
file1.txt:
id|no|cde
a|4|7
b|3|2
c|8|8
d|8|9
file2.txt:
id|no|cde
a|4|6
b|2|2
c|8|8 (1 Reply)
Hi guys, looking for some help with a way to compare data in two files but with some conditions.
example,
File 1 consists of
site1,10.1.1.1
site2,20.2.2.2
site3,30.3.3.3
File 2 contains
site1,l0.1.1.1
site2,50.1.1.1
site3,30.3.3.3
site4,40.1.1.1
I want to be able to match the... (1 Reply)
Hi,
I have a file containing a list of codes, followed by a description, such as below:
008.0,ESCHERICHIA COLI
008.1,ARIZONA
008.2,AEROBACTER AEROGENES
008.6,ENTERITIS DUE TO SPECIFIED VIRUS
008.8,OTHER ORGANISM, NOT ELSEWHERE CLASSIFIED
008,INTESTINAL INFECTIONS DUE TO OTHER ORGANISMSI... (6 Replies)
Discussion started by: carlr
6 Replies
LEARN ABOUT CENTOS
wdmd
WDMD(8) System Manager's Manual WDMD(8)NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if a single test fails 5-6 times in row,
the watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
The wdmd init script will load the softdog module if no other watchdog module has been loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
Test Source: scripts
wdmd will run scripts from a designated directory every test interval. If a script exits with 0, the test is considered a success, other-
wise a failure. If a script does not exit by the end of the test interval, it is considered a failure.
OPTIONS --version, -V
Print version.
--help, -h
Print usage.
--dump, -d
Print debug information from the daemon.
--probe, -p
Print path of functional watchdog device. Exit code 0 indicates a
functional device was found. Exit code 1 indicates a functional device
was not found.
-D
Enable debugging to stderr and don't fork.
-H 0|1
Enable (1) or disable (0) high priority features such as realtime
scheduling priority and mlockall.
-G name
Group ownership for the socket.
-S 0|1
Enable (1) or disable (0) script tests.
-s path
Path to scripts dir.
-k num
Kill unfinished scripts after num seconds.
-w path
The path to the watchdog device to try first.
2011-08-01 WDMD(8)