05-07-2013
There should be no reason to escape -. Perhaps you could try double-quoting $LINE in the test.
I'm not sure the -ne test is a great idea, if you expect $LINE could contain non-numeric data.
What shell are you using (looks like an AIX KSH error number)?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi
I am getting few messages when trying to run my script from the following lines in the script
if test
then
// SomeCode
fi
The messages are as follows:
testing.sh: OBLIGOR_GROUP_ID: 0403-012 A test command parameter is not valid.
testing.sh:... (5 Replies)
Discussion started by: skyineyes
5 Replies
2. Shell Programming and Scripting
Hello,
Getting error "A test command parameter is not valid" when trying to run the code below under /sbin/sh
AA = "12:00"
CHK=$(date +"%H:%M")
if
then
print "Yes"
fi
Getting 2 errors:
1) "AA: not found"
2) "Specify a parameter with this command"
Thanks,
IS
Please... (5 Replies)
Discussion started by: schureki
5 Replies
3. UNIX for Advanced & Expert Users
I'm using Korn shell. I'm doing an IF TEST for lots of characters and don't know how to also check for single quote and parentheses and slash. I'm reading a file and some records have garbage characters in them. The following works, but how do I add single quote, parentheses and slash to the IF... (3 Replies)
Discussion started by: sboxtops
3 Replies
4. Shell Programming and Scripting
Hey Guys,
I have a program that populates a database based on input I feed it.
so it would look like:
cmd arg1 arg2 ... argN
Now some of the arguments have special characters in them so I wrote a small script to pull the args and wrap them in quotes ('arg'). The problem is sometimes... (10 Replies)
Discussion started by: aaron0001
10 Replies
5. Shell Programming and Scripting
Hi all,
I would like to ask if there's something wrong with my if - else condition, i couldn't run the script perfectly due to the error in my if - else condition stating that "test: 0403-004 Specify a parameter with this command."
below is the snippet of my script
if && && ]
then echo... (5 Replies)
Discussion started by: jihmantiquilla
5 Replies
6. Shell Programming and Scripting
Hello,
I'm trying to write a simple (korn) shell script which is called from the command line with some parameters. But one of the parameter contains a "!" sign. For example: myscript.ksh foo bar foo!bar
When I call the script like above I always get an error. So I tried to wrap the... (1 Reply)
Discussion started by: merlinhst123
1 Replies
7. Shell Programming and Scripting
Hi, im asking for help with the next script:
echo ^;
then
if
then
printf "\033
query1.sh:
export TERM=vt100
export ORACLE_TERM=at386
export ORACLE_HOME=/home_oracle8i/app/oracle/product/8.1.7
export ORACLE_BASE=/home_oracle8i/app/oracle
export... (8 Replies)
Discussion started by: blacksteel1988
8 Replies
8. Shell Programming and Scripting
Hi all,
Case 1 :
A=88^M
&& echo "PASS"
Result:
PASS
Case 2:
A=88
&& echo "PASS"
Result:
PASS
I would like to know why Case 1 and Case 2 got the same result? What make ^M ignored ?
Thanks in advance. (6 Replies)
Discussion started by: montor
6 Replies
9. Shell Programming and Scripting
How to match a shell variable that contains parenthesis (and other special characters like "!")
file.txt contains:
Charles Dickens
Matthew Lewis (writer)
name="Matthew Lewis (writer)";
awk -v na="$name" ' $0 ~ na' file.txt
Ideally this would match $name in file.txt (in this... (3 Replies)
Discussion started by: Mid Ocean
3 Replies
10. Shell Programming and Scripting
If I have a file like the following
abc.1
abc
abc_1
abc..1
abc*1
abc@1
abc def ghr
def......
ddef 5466 def ed
def** 123445
I`m trying to find exact words from the list
abc
def (4 Replies)
Discussion started by: ritakadm
4 Replies
LEARN ABOUT DEBIAN
specrb
SPECRB(1) SPECRB(1)
NAME
specrb - standalone test runner for test/spec and Test::Unit test suites
SYNOPSIS
specrb [OPTIONS] [FILES | -a ] [-- untouched arguments]
DESCRIPTION
The Ruby script specrb allows you to run tests written with test/spec from the command line. It can also be used for plain Test::Unit test
suites. You can either specify the names of the test files you want to run, or let specrb find automatically all the tests in your project,
by using the -a switch (see TEST/SPEC OPTIONS below).
You can also use various options on the command line to pass parameters to the Ruby interpreterm or to modify the behavior of test/spec
and/or test/unit.
RUBY OPTIONS
-e, --eval LINE
evaluate a LINE of code
-d, --debug
set debugging flags (set $DEBUG to true)
-w, --warn
turn warnings on for your script
-I, --include PATH
specify $LOAD_PATH (may be used more than once)
-r, --require LIBRARY
require the LIBRARY, before executing your script
TEST
/SPEC OPTIONS:
-s, --specdox
do AgileDox-like output
--rdox
do AgileDox-like output with RDoc formatting
-a, --automatic
gather tests from ./test/, include ./lib/
TEST
::UNIT OPTIONS:
-n, --name NAME
runs tests matching regexp NAME
-t, --testcase TESTCASE
runs tests in TestCases matching regexp TESTCASE
COMMON OPTIONS
:
-h, --help
show a message similar to this manpage
--version
show version
AUTHORS
The test/spec library has been written by Christian Neukirchen <http://purl.org/net/chneukirchen>.
This manual page, inspired by the help message of specrb, has been written for the Debian Project by Cedric Boutillier (but may used by
others).
2012-06-26 SPECRB(1)