01-04-2011
Quote:
Originally Posted by
adshocker
does that mean i have an older version of shell that prevented me from using sh?
You probably have older version of bourne shell in which string operations doesn't work.
When you say "sh" that means bourne shell.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Need Help... I am getting a bad substitution error on my script on a Solaris Server. However the script has been proven to work on HPUX and Solaris servers...
#!/usr/bin/sh
#
# Set the location of the tzupdater.jar file
#
JAR=/tmp/tzupdater.jar # <<<<< UPDATE THIS LINE... (3 Replies)
Discussion started by: D_Redd74
3 Replies
2. Shell Programming and Scripting
Hi All,
We are in the process of Migrating from AIX 4 to Solaris 10 and getting a Few Errors.
I have been programming in shell but could never establish muself as an expert, hence please need you help.
I am Getting Bad Substitution error in my script, I have isolated the issue and its... (6 Replies)
Discussion started by: paragkhanore
6 Replies
3. Shell Programming and Scripting
Hello,
In bash I can use the following:
TMP=12345
MID=${TMP:1:1}
the expected result is: 2
but when using KSH I'm getting a ''bad substitution" error.
What is the correct syntaxin ksh?
Thanks (2 Replies)
Discussion started by: LiorAmitai
2 Replies
4. UNIX for Dummies Questions & Answers
#!/bin/bash
a1=( win 12,01,02,03,04 )
a2=( pre 04,05,06 )
a3=( msn 06,07,08,09 )
Given the above arrays, I want the script to return/echo the following in a loop;
win
12,01,02,03,04
pre
04,05,06,07
msn
06,07,08,09
But I can't get it to do as such.
I've tried; (2 Replies)
Discussion started by: Muhammad Rahiz
2 Replies
5. Shell Programming and Scripting
Hi All,
I'm building a new shell script but i'm facing a problem with one line which is giving "bad substitution" error. Please assist
script lines:
#!/bin/sh
printf "%s: " "Occurrence DATE (YYYYMMDD)"; read DATE
shortdate=${DATE#??}
o/p:
./test1: bad substitution
This command is... (2 Replies)
Discussion started by: Dendany83
2 Replies
6. Shell Programming and Scripting
Why I get bad replace when using eval?
$ map0=( "0" "0000" "0")
$ i=0
$ eval echo \${map$i}
0000
$ a=`eval echo \${map$i}` !!!error happens!!!
bash: ${map$i}: bad substitution
How to resolve it ?
Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies
7. Shell Programming and Scripting
I have script data.sh which has following error.
Script Name : data.sh
#!/bin/sh
infile=$1
len=${#infile}
echo $len
texfile=${infile:0:$len-4}
echo $texfile
run command
./data.sh acb.xml
I get following error message: (5 Replies)
Discussion started by: man4ish
5 Replies
8. Shell Programming and Scripting
Hi I'm using ksh.
And i'm trying to get the substring like below.
but giving the following error
#!/bin/ksh
foo=teststring
bar=${foo:0:5}
echo $bar
And the error is
./sbstr_test.sh: bar=${foo:0:5}: bad substitution
what is wrong in this script. Please correct me
... (3 Replies)
Discussion started by: smile689
3 Replies
9. Shell Programming and Scripting
I want to get the last character from my machine name using the following code, the default shell is bash, the script runs in ksh.
I get 'bad' substitution error on running the script, but works fine if run using dot and space.
Why?
$ echo $0
bash
$ cat -n myenv.sh
1 ... (8 Replies)
Discussion started by: ysrini
8 Replies
10. Shell Programming and Scripting
Cant undestand :) why i have an error on line 2.it is working on my other boxes
#!/bin/bash
ret=$(echo Q | timeout 5 openssl s_client connect "${1`hostname`}:${2-443}" -ssl3 2> /dev/null)
if echo "${ret}" | grep -q 'Protocol.*SSLv3'; then
if echo "${ret}" | grep -q 'Cipher.*0000'; then
... (7 Replies)
Discussion started by: kenshinhimura
7 Replies
USE(1) User Commands USE(1)
NAME
use - Frontend to the Usepackage Environment Manager
SYNOPSIS
csh and derivatives:
source /usr/share/usepackage/use.csh
bourne shell and derivatives:
source /usr/share/usepackage/use.bsh
korn shell:
. /usr/share/usepackage/use.ksh
use [-vs] [-f file] package ...
use -l
DESCRIPTION
Usepackage is an environment management program. It is based on the principle of packages - collections of executables that share a common
set of necessary environment variables, such as PATH, MANPATH or LD_LIBRARY_PATH.
For each given package, use sources the appropriate environment information into the current shell. The environment information is speci-
fied in a configuration file, see usepackage(1).
OPTIONS
-v Output verbose information to the standard error stream.
-s Silence warnings for un-matched packages. This is useful in a shell rc script when a package is known not to be available on all
architectures that the shell is used on.
-f file
Specify an alternate initial configuration file.
-l List available packages and groups.
FILES
/usr/share/usepackage/usepackage.conf
The default configuration file.
/usr/share/usepackage/use.csh
Shell setup for csh and derivatives.
/usr/share/usepackage/use.bsh
Shell setup for bourne shell and derivatives.
/usr/share/usepackage/use.ksh
Shell setup for ksh.
/usr/bin/usepackage
The underlying Usepackage executable.
ENVIRONMENT
Other than the reading and re-definition of environment variables for package setup, use also uses the following environment variables for
user configuration:
PACKAGES_PATH Colon-separated path list giving the directories to search for configuration files. Shell-style tilde (~) user-directory
escapes are expanded.
HOME If present in the environment, this is used to provide the expansion for the tilde (~) user-directory.
SHELL If present in the environment, the last path component of this is used for shell matching (see SYNTAX) and detecting the
style of environment output that should be used, see usepackage(1).
COPYRIGHT
Usepackage Environment Manager
Copyright (C) 1995-2005 Jonathan Hogg
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., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
SEE ALSO
usepackage(1), csh(1), sh(1), ksh(1)
Usepackage $Date: 2005/12/11 16:42:09 $ USE(1)