Changes

From SME Server
Jump to navigationJump to search
462 bytes removed ,  08:40, 28 November 2007
no edit summary
Line 1: Line 1: −
Start the Openfire Messaging Server
+
wouldn't it be better to point the alias to /opt/openfire/documentation/docs instead of giving access to the openfire directory, the only purpose for this is to view the docs.
   −
/etc/rc.d/init.d/openfire start
+
# Openfire instant messaging documentation
   −
'''I believe it should be'''
+
Alias /openfire /opt/openfire/documentation/docs
   −
cd /opt/openfire/bin
+
<Directory /opt/openfire/documentation/docs>
 +
    AddType application/x-httpd-php .php .php3 .phtml
 +
    Options Indexes +Includes FollowSymLinks
 +
    order deny,allow
 +
    deny from all
 +
    allow from all
 +
</Directory>
   −
sh openfire.sh
+
# end of Openfire fragment
 
  −
or
  −
 
  −
./openfire.sh
  −
 
  −
to start openfire
  −
 
  −
I have also noticed that the openfire service is not loading on startup
  −
 
  −
if i was to access or go to http://yourserver:9090 the admin console will not load, only if I was to load it manually by running the following commands, this has to be done each time after a reboot or opening and closing the command console
  −
 
  −
cd /opt/openfire/bin
  −
 
  −
./openfire.sh
  −
 
  −
or sh openfire.sh
  −
 
  −
I'm trying to locate my old notes, I'm sure the only way I got around this was to load openfire from source and install from that way, will double check that
  −
 
  −
I do remember, there was a reason why I used the source files to install openfire, it was because of the reasone above, the service will not load on startup, even though it is in /etc/rc.d/rc7.d
  −
 
  −
May I ask, what was wrong with setup procedures that i had in the first place
      
Russell
 
Russell
276

edits

Navigation menu