Filter
Top Products
ApplianceWare v.5.3 Complete FAQ – February 24, 2004 – Page 14 of 30
Optifacio Software Services, Inc.
NOTES
a) System-wide installation (i.e. performed from root user) is not recommended since it may
cause misc. access problems which are described in question 1.1.6.
b) A copy of Java Runtime Environment is included within the ApplianceView installation. It
will not intersect with any other Java Runtime Environment version that you may have on your
machine.
c) Please use Uninstall_ApplianceView symbolic link (or run Uninstaller directly from
installation folder) in order to remove ApplianceView from your computer. It ensures that all the
files are removed correctly.
1.3.3 ApplianceView crashes at startup with exit code 139 or segmentation fault. What's
wrong with it?
The problem may be in Java machine configuration. You should edit JVM configuration file,
and place the classic Java machine onto the top of the list of available machines. Assuming that you
have installed ApplianceView into ~/ApplianceView, the configuration file can be located at the
following path: ~/ApplianceView/jre/lib/jvm.cfg.
1.3.4 I have launched ApplianceView for the first time, and I cannot see my newly-
installed ApplianceWare server on the list. What should I do?
There can be several reasons for this behaviour.
• You have no DHCP server on the net. In this case, please run the linrouter.sh script from
the place where you have selected to create shortcuts during ApplianceView installation
(typically, it is your home directory when performing a per-user installation), type in your
user password at the password prompt (if any), and only then proceed with ApplianceView
startup. Your server should appear on the list of local appliances in ApplianceView in this
case. The server name will be “HOSTxxxxxx” (without quotes), where “xxxxxx” (without
quotes) stands for first six digits from MAC address of the NAS unit. Please note that you
should be included into the sudoers group in order to run the linrouter.sh script and