Hi everybody,
I tumbled into the following problem when trying to run wildfire on DEBIAN-40r0.
when starting the wildfire-script with parameter start I got a message saying that .install4j was a directory, which was absolutely correct. The message occoured in line 65 of the startup-script as the line stated ther tried to echo whatever content to that “file”, which actually was a directory.
So I simply changed the name of the file from .install4j to .install4j.db and thats it. Now it works for me on the debian installation. Additionally I defined the environment variable INSTALL4J_DB_FILE, which allows one to set the name of the file in ones profile-file, as I currently do.
This is the diff-for the script:
— wildfire.old 2007-04-24 12:25:54.000000000 +0200
+++ wildfire 2007-04-24 12:11:06.000000000 +0200
@@ -4,14 +4,14 @@
-
INSTALL4J_JAVA_HOME_OVERRIDE=
-
Uncomment the following line to add additional VM parameters
-
INSTALL4J_ADD_VM_PARAMS=
-JAVA_HOME=/opt/jdk1.5.0_06
+# Uncomment the following line to respecify the location of the install4j-cache.
+# INSTALL4J_DB_FILE=".install4j.db"
read_db_entry() {
if [ -n “$INSTALL4J_NO_DB” ]; then
return 1
fi
- db_file=$HOME/.install4j
- db_file=$HOME/$INSTALL4J_DB_FILE
if [ ! -f “$db_file” ]; then
return 1
fi
@@ -156,7 +156,7 @@
read file_jvm_home < “$app_home/.install4j/pref_jre.cfg”
test_jvm “$file_jvm_home”
if [ -z “$app_java_home” ] && [ $tested_jvm = “false” ]; then
-
rm $HOME/.install4j
-
rm $HOME/$INSTALL4J_DB_FILE
test_jvm “$file_jvm_home”
fi
fi
@@ -197,7 +197,7 @@
read file_jvm_home < “$app_home/.install4j/inst_jre.cfg”
test_jvm “$file_jvm_home”
if [ -z “$app_java_home” ] && [ $tested_jvm = “false” ]; then
-
rm $HOME/.install4j
-
rm $HOME/$INSTALL4J_DB_FILE
test_jvm “$file_jvm_home”
fi
fi
@@ -207,7 +207,7 @@
echo No suitable Java Virtual Machine could be found on your system.
echo The version of the JVM must be at least 1.5.
echo Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
- echo You can also try to delete the JVM cache file $HOME/.install4j
- echo You can also try to delete the JVM cache file $HOME/$INSTALL4J_DB_FILE
exit 83
fi
I Hope this bug was not reported before and this helps a bit to solve it.
Best Regards
Anardil