This is because the launcher script assumes that you have an /etc/bashrc where your CLASSPATH environment variable is initialized.
You can solve the issue editing the $ARCHIVING_ROOT/device/linux/*Archiver script and replacing this line:
source /etc/bashrc
by these lines (it will add all archiving .jar files to classpath):
ARCHIVING_ROOT=/wherever/you/installed/archiving
for file in `find $ARCHIVING_ROOT/lib/java -maxdepth 1 -iname "*.jar"` ; do
CLASSPATH=$file:$CLASSPATH;
done
Well, basically the problem was that ARCHIVING_ROOT and CLASSPATH environment variables must be properly defined before launching the devices.
In our case we prefer to not set the variables in bashrc as we may use different classpaths for different applications; so it is up to you whether you want to use /etc/bash.bashrc, /etc/bashrc or directly define the variables in the launcher script as we do.
Ok, thanks.
In fact, the complete message we got was the following :
shell terminal$./HdbArchiver 01
./HdbArchiver: 8: ./HdbArchiver: source: not found
./HdbArchiver: 19: ./HdbArchiver: [[: not found
./HdbArchiver: 27: ./HdbArchiver: [[: not found
Error: Could not find or load main class HdbArchiver.HdbArchiver
If I remember well, the solution of dash was because of the first 3 lines. It solves the last one which seems to be a side effect.