ConferenceRoom is presently available for Linux /
Intel and OSX / Intel. UNIX releases of ConferenceRoom
are packaged as compressed tar files. They include
an installer but do not facilitate automatic upgrades.
We provide the release in .tar.gz format.
It can be unpacked several ways. If the file's name
is file.tar.gz, and you have GNU tar, you should
be able to type tar xvfz file.tar.gz and unpack
it. If you have GNU gzip, you should be able to type
gunzip -c file.tar.gz | tar xvf -. Alternately,
you can unzip it with gunzip file.tar.gz and
then unpack it with tar xvf file.tar.
This should create a new directory containing the
ConferenceRoom distribution. Inside this directory
will be a README file. Also included is a file
called RELEASE with information about this
release of ConferenceRoom, and a file called PLATFORM
with any special problems or issues with your version
To run the installed, cd into the ConferenceRoom
directory that was just created. Then type ./install.
Simply answer the questions, and ConferenceRoom will
be installed and configured enough to get it running.
When you wish to upgrade to a newer version of ConferenceRoom,
we strongly advise you to use a procedure that protects
your previous version of ConferenceRoom. The files
that you typically need to copy from your current
version of ConferenceRoom into your new one (because
they contain your configuration information) are db/confroom.conf,
startcr, db/chan.db, db/nick.db, and db/webpass.sav.
Don't worry if you don't have any of the last three
We recommend you first unpack the new version of
ConferenceRoom. It will put itself in a new directory.
Then copy over the files listed above (and any others
you may have customized). You will then have to edit
'startcr' to reflect the new path in two places. You
should then be able to stop the currently running
copies of crchat, crws, crldap and crserv
and start the new version of 'startcr'.
You can then test the new version of ConferenceRoom.
If you notice any problems, you should be able to
shut down the new version and restart the old version.
Note that you must not attempt to edit the confroom.conf
file while ConferenceRoom is running. It will not
work. You also must not kill ConferenceRoom immediately
after making configuration changes. You must wait
at least two minutes for the changes to be saved.
We recommend you use the /DIE command, which
is always safe.
If you'd like to make sure the various servers remain
running even after a reboot or crash, you can add
'startcr' to your crontab. How this is done varies
from machine to machine, but a typical way to do this
would be as follows:
Create a file called cron containing the line
6,21,36,52 * * * * /full/path/to/startcr
Then type crontab cron. Note that this will
wipe out any other cron jobs you (the user you are
running as) had scheduled. You may want to check with
crontab -l first to make sure you don't have
We do not recommend running 'startcr' more often
than every five minutes. Also, if you're not using
CRServices or not using WMws, you should remove them
from the 'startcr' script. Removing the ws will stop
the web server from attempting to start and removing
the sv will stop services from attempting to start.
We strongly recommend shutting down ConferenceRoom
itself cleanly by use of the /DIE command.
CRServices will shut itself down cleanly when ConferenceRoom
dies, so there is no need to do anything special to
shut it down. If you just want to stop services, we
recommend issuing a /SQUIT command.
You can use kill to shutdown the various servers;
however, this is not recommended. Killing ConferenceRoom
can result in configuration changes, server bot locked
topics, and server bot locked modes not being saved.
Killing services can result in recent changes to registered
nicknames and channels not being saved. (ConfRoom
will shutdown cleanly on a SIGHUP.)
If you do decide to use kill, you can find
out the PIDs of the various services by looking at
their .pid files in the programs directory.
Please beware that those .pid files might be
old, and it's always possible another process was
created with that same PID. So please be careful not
to kill the wrong process! Be doubly careful if issuing
a kill command as root. One typo can bring
down your system such that it cannot be recovered
CR supports -stop as a flag to stop a server.
With this you can go into the ConferenceRoom directory
and type: ./programs/ConfRoom -stop to shut
down CR cleanly. The same technique will work for
the web server and services. Newer installers create
a stopcr script to automate this.