Please see the file COPYING for the GNU Public License, under which
this software is released.

1) check slfprefs.h for path names you may wish to change,
	along with system messages and other options,
	such as shadow password support, and the AUTO_ACCEPT_GUESTS option.

2) If you need shadow password support, go to Makefile-shared and
	uncomment the line CFLAGS += -DUSE_SHADOW, and make sure to
	run slforum as root.  Note that if you choose PAM in step 3
	below, you don't need to do anything special to get shadow
	password support, and you don't need to run as root to
	authenticate users.

3) Symlink to the proper Makefile
	(Makefile-linux, Makefile-solaris-2-6, Makefile-linux-pam, 
	 or Makefile-solaris-2-6-pam):
	ln -s makefile-for-your-system Makefile
	Running SLForum under Redhat 6.x, or any other system using MD5
	passwords, requires PAM support.

4) make

5) you now have the slforum executable; move it to where you want
	to run it and set permissions appropriately.

6) if you're using PAM, copy slforum.pam to where it's needed:
	cp slforum.pam /etc/pam.d/slforum
	(note no .pam extension on the destination file)
	Be sure it's owned by root, not you, if you weren't root when you
	untarred, compiled, and copied that file over.

7) If you're running forum as root, you should make the directory
	/var/lib/slforum which will hold user prefs, or whatever directory
	you've defined in slfprefs.h for PREFSFILE and PREFSFILE_fallback.
	Give it mode 700 (drwx------) so folks can't snoop on each other's
	preferences, whisper ban lists, etc.
	If you want some users to be able to use the !lock command,
	create /var/lib/slforum/lockout-users, in which go usernames of those
	allowed to !lock, each on its own line.

8) start a test run with
	slforum -nofork
   (from another window)
	telnet localhost 7777

   It should allow you to log in and type commands.

   In particular, please try
	!roll 15
   If this produces "please enter a positive number", you have a buggy egcs
   or gcc version.  Go back to slfprefs.h, uncomment the line for
   #define EGCS_ATOI_BUG_WORKAROUND
   and re-make.

   Otherwise, when this bores you, go to the window from which you started the
   test run and hit ctrl-C.

   Normally, you'll start the program with
	slforum 7777
   or
	slforum 7777 /path/to/logfile
   if you want to append to a logfile all public chat.  PRIVATE WHISPERING
   IS NOT RECORDED; we feel this is important to privacy.

   You should of course also pick a port your users can remember.
   7777 is the default port.

9) Clean out the temporary files from the directory you compiled SLForum in
   with the command
	make clean

10) Place the command to start the Forum in your rc.local, and never
   have to worry about it again!

11) If your users like to paste in ascii art, you may want to make a
    /tmp/.banners directory (chmod 1777 or similar) from which slforum
    will randomly choose a short file when the !banner or !spam command
    is used.


CAVEATS:
*  If run as root, slforum will write login and logout entries to your
   /var/log/wtmp file; this enables use of the "last" command to see who's
   logged into the Forum, similar to ftp or telnet:

quaestor% last -5
demaria  pts/10       nullpointer      Mon Nov  8 02:10   still logged in
dracofav ftp          win5.fcms.academ Mon Nov  8 02:05 - 02:05  (00:00)
dracofav pts/7        win5.fcms.academ Mon Nov  8 01:16   still logged in
demaria  slforum/916  nullpointer      Mon Nov  8 00:39   still logged in
dracofav ftp          syru47-247.syr.e Mon Nov  8 00:35 - 00:36  (00:00)


*  Root can't log into the Forum.  This prevents attempts to guess the root
   password by running a password-guesser on the port running slforum.


That should be it!  Enjoy.

Cheers,
-Jeremy Monin, Dan Chin, Matt Lochansky
 forum@shadowlands.org
 http://shadowlands.org/forum/
