Previous Chapter
Next Chapter
Table of Contents
Index

Installing
   Binary distribution
   Source distribution
Finishing
Automatic restart
Running
   Stop
   Debuglog

Installing Roxen Challenger


Installing

If there is a binary distribution available for your computer, move on to "Installing the Binary distribution". Otherwise, move on to "Installing the Source distribution".

Binary distribution


  1. cd

    to the working directory from where you want Roxen to be installed and place the archive there.

  2. Issue the following commands to unpack the archive:

    gunzip Roxen_1.2.tar.gz
    tar -xf Roxen_1.2.tar

Now move on to the section on finishing the installation on page X.

Source distribution


  1. cd

    to the working directory from where you want Roxen to be installed and place the archive there.

  2. Issue the following commands to unpack the archive:

    gunzip Roxen_1.2.tar.gz
    tar -xf Roxen_1.2.tar

  3. Type:

    cd Roxen_1.2

    to change to the new directory. This directory should contain at the very least four directories:

    server (Roxen server source), pike (the Pike interpreter), extern (misc. programs used by Roxen) and tools (misc tools). See README for more information about the directory structure.

  4. Type:

    ./configure --prefix=«desired_base_path_to_Roxen»

    (defaults to /usr/local, thus placing Roxen in /usr/local/roxen/)
    This will take a while, when it's done type:

    make

    You will now see dozens of lines indicating a lots of checks being made. When the checks are completed type:

    make install

    You should now see another dozens of lines indicating the files being compiled. Note that it will take some time to compile everything. On a Sun Sparc 5 with 128 Mbytes of memory it takes around half an hour.

You can later on move the 'roxen' directory that was created when you typed 'make install' to anywhere in your filesystem. Roxen does not keep any absolute paths.

When the compilation has been completed, move on to the section "Finishing the installation".

Finishing

  1. Type:

    cd /«desired_base_path_to_roxen»/roxen/server/

  2. Start the install script by typing ./install
  3. Answer the simple questions and wait for your client.

As soon as the installation is done you will be prompted for User name and Password. Fill in the desired values and move on to Configuring Roxen. Consider also joining the Roxen mailing list by sending an email to roxen-request@idonex.se, with the subject: subscribe.

For more information about Roxen, read the online documentation at http://roxen.com/.

Automatic restart

You can, if you wish, make Roxen start automatically when the computer has rebooted. Depending on which operating system you are dealing with, type in one of the following command lines:
  • BSD
    Edit /etc/rc.local, and add
    (cd /«desired_base_path_to_roxen»/roxen/server/;./start)

  • SysV (eg Solaris 2)
    Copy tools/init.d_roxen to /etc/init.d/roxen.
    cp tools/init.d_roxen /etc/init.d/roxen

    Make a symlink in /etc/rc3.d
    ln -s /etc/init.d/roxen /etc/rc3.d/S90roxen

  • DigitalUnix, HP-UX
    Copy tools/init.d_roxen to
    /sbin/init.d/roxen.
    cp tools/init.d_roxen /sbin/init.d/roxen

    Make a symlink in /sbin/rc3.d
    ln -s /sbin/init.d/roxen /sbin/rc3.d/S90roxen

  • Linux/RedHat
    Copy tools/init.d_roxen to
    /etc/rc.d/init.d/roxen.
    cp tools/init.d_roxen /etc/rc.d/init.d/roxen

  • Make a symlink in /etc/rc.d/rc3.d ln -s
    /etc/rc.d/init.d/roxen
    /etc/rc.d/rc3.d/S90roxen
In most cases you have to edit tools/init.d_roxen and update roxenhome to your «desired_base_path_to_roxen» location.

Running

Stop

The easiest way for most users to stop Roxen is by login to it's Configuring interface and choose 'restart' from the session-menu. There's also possible to stop your Roxen from the autostart-script.
Change directory to either your Roxen source directory.
Type: sh tools/init.d_roxen stop
Or change directory to /etc/init.d/ or (if on a RedHat-system) /etc/rc.d/init.d/
Type: sh roxen stop

Debuglog

Roxen writes to the debuglog which is located in «desired_base_path_to_roxen»/logs/debug/
Previous Chapter
Next Chapter
Table of Contents
Index