Also it's usually a good idea to add double quotes around the values; you will get very confusing error messages if either of the variables would turn out to contain an empty string (or a vast array of other possible problematic values).
In real-world scripts, you frequently see a leading X added to the values, to guard against some of the remaining problematic scenarios (if $VAR1 has a value containing a dash as the first character, for example).
For these reasons, I personally tend to recommend case over if for string comparisons.
This is a search script that I have developed. It finds the records that I look for. However the only thing I want the program to do now is to display a message such as 'Not Found' to appear when a record is not found. So far when a search doesn't display a record, the screen is blank.
... (14 Replies)
hi all. i have a little problem. im basically reading input from the user from the keyboard into the variable "phonenumber". I want to do a little error check to check if the user doesnt enter anything in for the value phonenumber.
i had this:
read phonenumber
if
then
.....
else
........ (2 Replies)
Hi everyone, I am facing to one shell script problem, which is as following
Write a shell script that:
Takes a number of arguments.
For each argument, print out all files in the current directory that contain this substring in their name.
I know I need to use grep for the second... (7 Replies)
Hi all,
I have set up a simple awk script to calculate the average of values that are printed out a number of times per second (the number of time the printing occurs varies). The data is of the format shown below:
1 4.43
1 3.65
1 2.45
2 7.65
2 8.23
2 5.65
3 4.65
3 6.21
.. ..
120... (4 Replies)
#!/bin/csh
echo hello world
this is what i got in a text file called ss1.
i type "chmod 755 ss1.txt" to make it executable.
then when i type
ss1
or
ss1.txt
it says
"ss1 command not found"
what am i doing wrong? (19 Replies)
Hello forum memebers.
can you correct the simple while program.
#! /bin/ksh
count=10
while
do
echo $count
count='expr$count-1'
done
I think it will print 10 to 1 numbers but it running for indefinite times. (2 Replies)
Warning! I'm ridiculously new at all this, so pardon my ignorance...
I have a very simple script which is intended to search a hosts file when given a partial hostanme or ip address. The if the partial hostname/ip given is unique, the script automatically logs the user in to that host. If... (6 Replies)
I want to find and replace string from files present in one directory.
user will input the string to be searched and to replace .
Here is my program but Not working
echo "Enter Old domain name:"
read old
echo "Enter New domain name:"
read new
grep -rl '$old' /var/www/ | xargs sed -i... (4 Replies)
Hello,
when running the scripts below I am not getting message bb2.
Can you please help?
#!/bin/bash
TLOG=/tmp/bb/amatest.log
FTPRESULTS=/tmp/bb/amlist
export TLOG FTPRESULTS
>$TLOG
>$FTPRESULTS
echo bb1
sftp -oPort=2222 XXXXXXXXXXXXX@sftp.userssedi.com <<EOF
cd... (5 Replies)
Discussion started by: biljana
5 Replies
LEARN ABOUT CENTOS
error::pass1
ERROR::PASS1(7stap)ERROR::PASS1(7stap)NAME
error::pass1 - systemtap pass-1 errors
DESCRIPTION
Errors that occur during pass 1 (parsing) usually mean a basic syntax error of some sort occurred in the systemtap script. There are sev-
eral classes of problems possible:
plain syntax error
The systemtap script parser detects a large variety of errors, such as missing operands, bad punctuation. It tries to list what
kinds of tokens it was expecting to see, and will show the region of the source code with the problem. Please review the stap(1)
man page and/or the tutorial, to correct the script's syntax.
grammar ambiguities
There is at least one known ambiguity in the systemtap grammar. It relates to the optionality of ; (semicolon) separators between
statements, and the ++ and -- increment/decrement operators. If the parser indicates an error, consider adding some explicit ; sep-
arators between nearby statements and try again.
missing command line arguments
A systemtap script that uses the $N and @N constructs for substituting in command-line options may fail if not enough options were
given on the stap command line.
compatibility changes
Some versions of systemtap have changed the language incompatibly, for example by adding the try/catch keywords for exception han-
dling. In such cases, rerun systemtap with the --compatibility=VERSION option, substituting the last systemtap version where your
script was known to work. You may also check the release-history NEWS file for compatibility changes.
GATHERING MORE INFORMATION
Increasing the verbosity of pass-1 with an option such as --vp 1 can help pinpoint the problem.
SEE ALSO stap(1),
error::reporting(7stap)ERROR::PASS1(7stap)