when declaring a variable e.g.
export DAYS
what checking / how can i check that the value assigned only contains numeric characters or integers ? (1 Reply)
I'm trying to run a ksh script with a case condition to handle parameters.
#!/bin/ksh
db_start(){
*code
}
db_shut(){
*code
}
case "$1" in
up)
db_start TRNG
;;
down)
db_shut TRNG
;;
*)
echo "Usage: $0 { up | down }" (3 Replies)
Hi
I made a small script which uses ksh.
When i run the script then i get the following error
However when i run each of the commands on the commandline they get executed and provide the desired output. i cant figure out why the script is not running.
Kindly Help
Thanks in... (3 Replies)
i have following in block
if
then
echo "Exclusion criteria"
else
echo "Not exclusion criteria"
fi
now above block runs fine if value of variable line_by_line is "00000000dfahfahfahfahsfhasfhafhahfahfahf" but same block gives error if value is "0000000000202000501000069BAG ICE ... (1 Reply)
Hi All,
I have got a problem. I have written a Shell script which cuts some information from the file a and puts it in file b. But i get this error when i execute the shell script.
This is what i have written in the script.
#! /usr/bin
cd /test
ls $2 > a
cut -f 1 -d '.' a > b
When i... (2 Replies)
Hi,
I have the following issue while replacing text in a file usind sed
$ cat file
$ One,ABCD\XYZ,Server one
i want to replace ABCD\XYZ with another text SERVER. with ABCD\XYZ stored in a variable.
#!/bin/ksh
VAR=ABCD\XYZ
echo $VAR
cat file | sed 's/'"$VAR"'/SERVER/'
... (14 Replies)
Hi All,
I have a fixed-width datafile from which i need to extract value/string starting from some position to the specified length in each of the lines.
awk '{print substr($0,x,y)}' datafile --- is working fine
but
awk 'BEGIN{a=0}{a=substr($0,x,y);print $a}' datafile ---is giving... (3 Replies)
Script A:
#!/bin/ksh
/usr/bin/mail -s "case 4" g@f.com <testF5Email.inp
Script B:
#!/bin/ksh
qq="-s \"case 4\" cstsang@hko.hksarg"
/usr/bin/mail $qq<testEmail.inp
Script A working properly where Script B cannot.
The error message as the following:
There is a missing '"' character... (3 Replies)
Discussion started by: cstsang
3 Replies
LEARN ABOUT XFREE86
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)