03-21-2012
Good catch. I missed it somehow.
Thanks,
Sri
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello forum members.
please go through the below mentioned issue and let me know the right solution.
I have to write a script which runs another script .the executable script take input parmeters.so iam writing the the script below .
Sample Code:Begins
#! /bin/ksh
echo " enter... (2 Replies)
Discussion started by: rajkumar_g
2 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am using the following code
#!/bin/sh
chris='rerun'
chris2=$1
echo "chris=$chris"
echo "chris2=$chris2"
if
then
echo "RERUN"
else
echo "NOT RERUN"
fi (6 Replies)
Discussion started by: chriss_58
6 Replies
3. Shell Programming and Scripting
Hi, Unix Gurus,
I got some issue with my script.
#!/usr/bin/ksh
while read newstatus
do
if ; then
echo "It is finished "
else
echo "Not Finished"
fi
done <checkresult.txt
basically, I want to read one file (the file only contains one word, but it dynamically changed),... (2 Replies)
Discussion started by: ken002
2 Replies
4. Shell Programming and Scripting
hi,
I have some problems in my simple script about the redirect echo stdout command inside a condition. Why is the echo command inside the elif still execute in the else command
Here are my simple script
After check on the two diff output the echo stdout redirect is present in two diff... (3 Replies)
Discussion started by: jao_madn
3 Replies
5. Shell Programming and Scripting
Hi
I am extracting a column value(DESCRIPTION) from one table and passing it to another db2 statement in a shell code to fetch some value(ID) but the value when passed in where condition is taking as newline+value.
Please find the out put when executed:
+ echo description is ::::... (1 Reply)
Discussion started by: msp2244
1 Replies
6. Shell Programming and Scripting
hi,
i am using a simple condition
end_ct=`sqlplus -s $ORACLE_USER/$ORACLE_PASS@$ORACLE_SID << EOF
select description from bravo_statistics
where trunc(time_stamp)=trunc(sysdate)-1
and description='END CAT';
EOF`
echo $end_ct;
echo... (30 Replies)
Discussion started by: lovelysethii
30 Replies
7. Shell Programming and Scripting
Hi
I am trying to do a "IF" Condition in UNIX where we compare EACH file size in a directory with a SIZE (Parameter passed)
If Each File size EXCEEDS parameter passed SIZE then we manipulate the file.
Somehow the IF condition do not work ?? (is this Variable decalration issue ??)
... (9 Replies)
Discussion started by: Pete.kriya
9 Replies
8. Shell Programming and Scripting
Getting syntax error when the condition after -o returns more than one file
if
then
echo "Found"
fi
output:
=>ls -l
total 5
-rw-rw-r-- 1 wes wes 0 Jun 25 04:51 a.done
-rw-rw-r-- 1 wes wes 0 Jun 25 04:51 a.zip
-rw-rw-r-- 1 wes wes ... (13 Replies)
Discussion started by: anijan
13 Replies
9. Shell Programming and Scripting
Solaris 11 ksh93 if condition issue
Has anyone run into issues with Solaris 11 with ksh93 if condition where it intermittently return wrong return code?
We did not see this issue in Solaris 10 with ksh88
Any thoughts? Thanks!
Solaris version: SunOS t52-ccc-28 5.11 11.2... (4 Replies)
Discussion started by: nugent
4 Replies
10. Shell Programming and Scripting
Hi everybody,
I must get trought a shell script 3 arguments.
1st argument = $1 (can take values REP1..4)
2nd argument = $2 (can take values A..Z)
3rd arguement = $3 (also can take values A...Z)
I've written this code :
#!/bin/bash
if
then
liste=/data/folder1
echo... (6 Replies)
Discussion started by: shellX
6 Replies
LEARN ABOUT NETBSD
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)
NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS
--help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO
lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN
Debian Utilities CHECKBASHISMS(1)