I was 100% sure...
As it used to work yesterday - or I've must have overseen this message due to all other error messages...
As you see, it's the exact same code, that had worked for over a year (5 years ago).
Maybe there was a security update or something?
But now thinking about it....
:doh:
That genrc.sh was to, well, generate an RC file, for which of course the $ had to be escaped....
Now, it's in the actual script already -> no need to escape...
Hello all,
I want to create a script that polls every hour a directory for the existence of a file. The file I look for is a `token` dropped by an external process at the completion of a successful FTP process. I wrote this script `checkfile.ksh`:
#!/usr/bin/ksh
if ] then
mailx... (5 Replies)
Hi,
i am getting following syntax error ...kingly advice why is it coming ??
#!/bin/bash
find . -name "common.log"
if ; then
echo "1"
fi
Himnashu@home /bin
$ ./a.sh
./a.sh: line 7: syntax error near unexpected token `fi'
./a.sh: line 7: `fi' (9 Replies)
Hi,
When I run the below shell script I'm getting the error " syntax error near unexpected token `"
Script:
REM :: File Name : Refresh_OTL.bat
REM :: Parameters : %1 - Region
REM :: : %2 - Cube Type
REM :: :
REM :: Notes :
REM ============================== set ENVIRONMENT... (2 Replies)
Guys ,
This is an output of my script errored out for "Syntax error near unexpected token `(' " Can someone tell me whats wrong with my script.
Below is my original script pasted.
#!/bin/bash
Script Creation Date 01/21/2010
Author baraghun
... (7 Replies)
Hi all,
Am very new to Unix and am currently Involved in Migrating some Shell Scripts from AIX 4 to Solaris 10.
While using teh for loop am getting the below error:
$ echo $SHELL
/usr/bin/ksh
$ for file in $(ls *SEBE*)
syntax error: `$' unexpected
while the same works without issue on... (4 Replies)
So I am trying to convert my bash script into ksh, and this is what I have in the file so far:
#!/bin/ksh
login()
{
if
then
sendcmd BETA
else
sendcmd "$(xxd -c 32 -g 0 ${ZETA_ZETA} | awk '{print $2}')"
fi
}
But when I run it:
$ ./test.sh ... (1 Reply)
I'm going mad not being able to get this to work. im assuming its only a simple mistake but its driving me bonkers trying to find it.
Please if you can help me it would save me pulling my hair out!!
Thanks
#!/bin/bash -xv
#
#Config
name="TEST Server"
+ name='TEST Server'... (6 Replies)
unzip file.zip
if ] ; then
echo "Success"
else
echo "Some failure."
fi ;
I tried many time to detect the unzip error, but it keep show the syntax error wherever how I change the syntac. Hope someone can help me fix the issue, thanks.
Please use code tags next time for your code and... (5 Replies)
I have written this in my script but while running i am getting syntax error `(' unexpected.
unload to "$BACKUP_DIR/n_fac_fid-$clliname" select * from n_fac_fid where fac_accesskey in (select fac_accesskey From n_fac_ap_fid where ap_clli="$clliname");
Any help appreciated. (3 Replies)
I am getting this error Syntax error: `]' unexpected. Did I do something wrong with elif? Does ksh not like double brackets?
if ]; then
#echo hi
source ~/.bashrc;
elif ]; then
#echo hi
source ~/.kshrc;
fi (5 Replies)
Discussion started by: cokedude
5 Replies
LEARN ABOUT DEBIAN
deweb
deweb(1) General Commands Manual deweb(1)NAME
deweb - strips away C & CWEB commands from CWEB sources
SYNOPSIS
deweb [ file1 file2 ... ]
DESCRIPTION
deweb filters away all C & CWEB commands from a CWEB source code. This leaves only the LaTeX code. This stripped code, in turn, may then be
passed to a suitable syntax checker for LaTeX, like ChkTeX and lacheck, or spell-checkers like ispell.
The chkweb tool, included in the ChkTeX distribution will do just this; writing similar scripts should be trivial.
When deweb strips away the C code from your CWEB source, it tries to preserve line breaks. This means that the error reports from <your
favorite tool> will be correct regarding to line numbers. In most cases, the column position will also be correct. This significantly sim-
plifies finding the errors in the LaTeX source (in contrast to the output from cweave, which output is truly difficult to figure anything
out from).
deweb accepts a list of filenames on the argument line, and will send its output to stdout. If no filenames are given, it will read from
stdin, acting as a filter. No options are currently accepted.
Macho users may try to pipe the output from deweb directly into LaTeX, theoretically, this should work. This would ease the debugging of
the LaTeX code significantly, as when LaTeX complains about wrong syntax, you'll be able to find the erroneous line much more easily. Don't
expect that the output looks very much like the final one, though.
deweb should now understand all correct CWEB opcodes. If it complains about not understanding a correct opcode, please inform the author.
DISTRIBUTION
Copyright (C) 1996 Jens T. Berger Thielemann
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation,
Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
ENVIRONMENT
No environment variables are used.
FILES
None.
AUTHOR
Jens T. Berger Thielemann, <jensthi@ifi.uio.no>
SEE ALSO cweave(1), perl(1), chktex, lacheck(1), ispell(1)BUGS
Doesn't even compile under Perl versions before perl v5. Unfortunately, this means that we can't even tell the user why we failed; Perl
will just complain about not being able to compile the regexps.
The program will try to swallow the whole input file at once, instead of processing it on a line-by-line basis.
7th Edition June 8, 1996 deweb(1)