02-02-2015
And , if you add i=`expr $i + 1` just before done ?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to check the script syntax with some sort of command...? Without running the script .
I'm using Sun Solaris (3 Replies)
Discussion started by: bjornrud
3 Replies
2. Shell Programming and Scripting
Hi All,
I have been fighting with a syntax error for the last 2 days, still haven't got the solution. Could you please help me, your help will be greatly appreciated.
In my script I am getting a error in a for loop, its similar to the one as is below.
for v_id in v1 v2 v3 v4
do... (8 Replies)
Discussion started by: rajus19
8 Replies
3. Shell Programming and Scripting
I get this error when I try to run my script
(BTW, this is a simple script I am supposed to write for my class)
$ menuscript
menuscript: syntax error at line 89 : `"' unmatched
$
Here is the code (Any help is greatly appreciated)
(Line numbers included)
1 #!/bin/ksh
2 ... (2 Replies)
Discussion started by: KindHead
2 Replies
4. Shell Programming and Scripting
Hello all, I am trying to write a little script to create a file and I keep getting the below error and cant see where my syntax mistake(s) is. please help...
the script:
FILE="/u/e477059/Unix_Machines/LISTS"
for X in `cat ${FILE}/list`
do
ssh $X "echo $X;
cd /var/tmp;
... (2 Replies)
Discussion started by: rookieuxixsa
2 Replies
5. Shell Programming and Scripting
Hi
I not sure what is wrong with my script... when I try to run it I get the follow error: "remove: syntax error at line 77: `end of file' unexpected" Thanks in advance for any help.
ans=y
while
do
while :
do
echo "Please enter a name that you... (3 Replies)
Discussion started by: simpsonjr
3 Replies
6. Shell Programming and Scripting
Hey guys keep having problems with the below script syntax error near unpexpected token '0' exit 0 I have two directorys backups and Usr in the usr i have sub dir's wp,ss,pic which i would like to back up (copy those directorys to the backups directory) with user acknowledgement from command line.... (2 Replies)
Discussion started by: Spartukus
2 Replies
7. Shell Programming and Scripting
I am have FTP syntax like below in my bash shell script
ftp -n <<END
open $Server
user $FtpUser $FtpPwd
cd $FtpPath
binary
put $Filename.gz
bye
END
Now I wanted to change this into SFTP. I tried... (4 Replies)
Discussion started by: sbmk_design
4 Replies
8. Shell Programming and Scripting
hello everyone
i am beginner on shell scripting .and i am working on my project work on ad hoc network
i wrote a batch (.sh) to do a looping and execute a tcl script i wrote before in each iteration ..but i got this problem "
syntax error near unexpected token `('... (1 Reply)
Discussion started by: marcoss90
1 Replies
9. UNIX for Dummies Questions & Answers
Hi guys i'd like to show you this code of my script, where i couldn't find this error
" #! /bin/bash
#copiabin.sh: copia todos los archivos ejecutables a bin
if
then
mkdir $HOME/bin
fi
# copia de archivos y contador N
N=0
for ARCH in *
do
if # Si el archivo es... (9 Replies)
Discussion started by: Newer
9 Replies
10. Shell Programming and Scripting
I added some fields to some existing code, and all was well. Just added a few more, and BAM. I've looked this over forever, but being a newbie to Python, I see NOTHING. The code generates syslog messages, and the new fields were added around "rtp_lapse*" . Any clues???
#!/usr/bin/python
... (4 Replies)
Discussion started by: gmark99
4 Replies
LEARN ABOUT DEBIAN
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)