The better approach is to get rid of the scripts and replace them with
ant based startup scripts as it is more portable, especially windows.
I would not expect sh to work against a ksh script across the board
myself anyways.
Knut Anders Hatlen (JIRA) wrote:
ksh scripts should be written in a more portable way
----------------------------------------------------
Key: DERBY-677
URL: http://issues.apache.org/jira/browse/DERBY-677
Project: Derby
Type: Bug
Components: Demos/Scripts
Versions: 10.2.0.0, 10.1.2.1
Reporter: Knut Anders Hatlen
Assigned to: Knut Anders Hatlen
Priority: Minor
The ksh scripts in the frameworks directory are written in a way which
is not totally portable. They use a syntax that is specific to ksh and
not understood by the standard Bourne shell. This prevents some
variants of Unix from running the scripts when you have the scripts'
path in your PATH environment variable.
These commands work:
ksh /path/to/scripts/ij.ksh
bash /path/to/scripts/ij.ksh
These commands might not work on some platforms:
sh /path/to/scripts/ij.ksh
/path/to/scripts/ij.ksh
ij.ksh # might not work even if /path/to/scripts is in PATH
The syntax that is not portable is
export VAR=value
Rewriting it to
VAR=value
export VAR
would make the scripts portable to all shells in the Korn and Bourne
shell family.
