test with two conditions (OR) Post: 302262897

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the...

2. Shell Programming and Scripting

How to check weather a string is like test* or test* ot test in if condition

How to check weather a string is like test* or test* ot *test* in if condition

3. Shell Programming and Scripting

Prefixing test case methods with letter 'test'

Hi, I have a Python unit test cases source code file which contains more than a hundred test case methods. In that, some of the test case methods already have prefix 'test' where as some of them do not have. Now, I need to add the string 'test' (case-sensitive) as a prefix to those of the...

4. Shell Programming and Scripting

Errors in if conditions with to many OR conditions

Hi ALL I have a script where in i need to check for several values in if conditons but when i execute the script it throws error such as "TOO MANY ARGUMENTS" if then msg="BM VAR Issue :: bmaRequestVAR=$bmaRequestVAR , nltBMVAR=$nltBMVAR , bmaResponseVAR=$bmaResponseVAR ,...

5. Shell Programming and Scripting

Shc : trying to test functionality "test" compiling but can not execute

I am testing shc to see if it would help with my need. Im at a point where Im trying to compile and test the "test.ksh" file that comes in the tar ball : shc-3.8.9> shc -v -r -f test.ksh shc shll=ksh shc =-c shc =exec '%s' "$@" shc = shc opts= shc: cc test.ksh.x.c -o test.ksh.x...

6. Shell Programming and Scripting

Shell test conditions

Are these shell test conditions in any man pages? I do not see them in bash or ksh man pages. The tests below are test conditions provided by the shell: -b file = True if the file exists and is block special file. -c file = True if the file exists and is character special file. -d file...

LEARN ABOUT DEBIAN

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 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.

       wdmd will exit if a watchdog driver is not 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.

       (Other test sources such as scripts executed each test interval may be added in the future.)

OPTIONS

       -D     Enable debugging to stderr and don't fork.

       -H num Enable (1) or disable (0) high priority features such as realtime scheduling priority and mlockall.
	      Default 1.

								    2011-08-01								   WDMD(8)