I am finding a few pieces of documentation to be contradictory, and it’s casuing me headaches.
In the current install documentation
link: http://www.igniterealtime.org/builds/openfire/docs/latest/documentation/install- guide.html#unix
it says:
Running Openfire in Linux/Unix
You can start and stop Openfire using the bin/openfire script in your Openfire installation:
- ./openfire
Usage: ./openfire {start|stop}
- ./openfire start
Starting openfire
If you would like to install Openfire as a service, two scripts are provided in the bin/extra
directory… yadda yadda
But in the “Openfire 3.3.0 to Openfire 3.3.1 Upgrade Guide”
link: http://wiki.igniterealtime.org/display/WILDFIRE/Openfire+3.3.0+to+Openfire+3.3.1 +Upgrade+Guide
It says:
Things to note
-
The new RPM installs Openfire as a service. That means that the server will be started when the OS is started and the server is stopped upon shutdown.
-
/opt/openfire/bin/openfire no longer exists. It was a start/stop script generated by install4j. Since we are no longer using install4j, it needed to go. Instead, we now have a more standard linux init script, /etc/init.d/openfire.
Yet when I installed from scratch from an rpm
rpm -ivh openfire-3.3.3-1.i386.rpm and subsequently
./openfire.sh
ls: /usr/java/j*: No such file or directory
Openfire 3.3.3
Admin console listening at http://127.0.0.1:9090
What gives?