if and test not working Post: 302658663

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

test command is not working

#!/bin/ksh size=3978132853 limit=100 if ;then echo exceeded limit fi This does not work though if i reduce 3978132853 to 397813285 it works any ideas and work around appreciated (SunOS 5.9 Generic_117171-02 sun4u sparc SUNW,Ultra-80 )

2. Solaris

How i test the UDP port is working?

Hi anybody know how to test out the UDP port working? cos UDP cannot use telnet to test... Sumemr

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

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

5. Shell Programming and Scripting

String == isn't working in [[-test

Hi. I'm new to this forum, my English perhaps is not so good, but here is my question: In bash you can use ] for tests, and how I understand it the variable names should be expanded automatically. So this should give "yes": xx=hello $ ] && echo yes || echo no no # not giving "yes" These two...

6. Shell Programming and Scripting

Use The Terminal To Test Arduino Is Working.

Hi all... (Apologies for any typos at all.) This is a step by step _script_ to check if your Arduino is talking to your Linux or Macbook Pro computer using the Terminal... It works on at least 3 Linux flavours and now the Macbook Pro... I hope you find it useful as a simple check for...

7. Shell Programming and Scripting

Test function not working

i am writing the following snippet and cannot figure out why the variable measType remains 0. it should be 1 I also tried "\#analog" and '\#analog' in the test statement and it still doesn't work. What is going on? bash$ measType=0 bash$ read line < 2iconfig.ini bash$ echo $line #analog...

8. UNIX for Advanced & Expert Users

Test -e not working as expected (by me)

I ran into the following and still do not understand entirely the rationale behind this. If someone could explain why things are as they are I'd be thankful. The following was tested on AIX 7.1 with ksh88, but i suspect that to be ubiquitous. In an installation routine i had to create a set of...

LEARN ABOUT CENTOS

gtester

GTESTER(1)							   User Commands							GTESTER(1)

NAME

       gtester - test running utility

SYNOPSIS

       gtester [OPTION...] [testprogram]

DESCRIPTION

       gtester is a utility to run unit tests that have been written using the GLib test framework.

       When called with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report
       utility.

OPTIONS

       -h, --help
	   print help and exit

       -v, --version
	   print version information and exit

       --g-fatal-warnings
	   make warnings fatal

       -k, --keep-going
	   continue running after tests failed

       -l
	   list paths of available test cases

       -m=MODE
	   run test cases in MODE, which can be one of:

	   perf
	       run performance tests

	   slow, thorough
	       run slow tests, or repeat non-deterministic tests more often

	   quick
	       do not run slow or performance tests, or do extra repeats of non-deterministic tests (default)

	   undefined
	       run test cases that deliberately provoke checks or assertion failures, if implemented (default)

	   no-undefined
	       do not run test cases that deliberately provoke checks or assertion failures

       -p=TESTPATH
	   only run test cases matching TESTPATH

       -s=TESTPATH
	   skip test cases matching TESTPATH

       --seed=SEEDSTRING
	   run all test cases with random number seed SEEDSTRING

       -o=LOGFILE
	   write the test log to LOGFILE

       -q, --quiet
	   suppress per test binary output

       --verbose
	   report success per testcase

SEE ALSO

       gtester-report(1)

GLib																	GTESTER(1)