home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
XOR_107.ZIP
/
SIMPLE.CFG
< prev
next >
Wrap
Text File
|
1995-06-03
|
16KB
|
333 lines
;============================================================================
;
; A SIMPLE sample CFG for XOR version 1.07
; This is only a very simple configuration file which doesn't
; reveel very much of the features implemented in xOR.
; Copyright (c) 1993,94,95 by Mirko K. Mucko
;
;============================================================================
;
; For better performance at runtime, your may remove all comments
;
;============================================================================
; MAINAKA and AKA define your main aka and additional akas. As second
; parameter, define a extension (3 chars). This extension is used on all
; text files to allow different responsed aka depending.
;============================================================================
MAINAKA 2:2433/920 TXT
;============================================================================
; Now, several files and pathes are defined. You may ommit the trailing
; backslash if you want.
;
; In multiline environment (SET TASK=...), the LOGFILE name is appended
; by the task number. "XOR.LOG" will become "XOR1.LOG" if TASK is set to "1".
;============================================================================
LOGFILE D:\TP\PRG\FIDO\XOR\XOR.LOG
OLILOGFILE D:\TP\PRG\FIDO\XOR\OLI.LOG
;============================================================================
; INBOUND is you *.pkt directory. xOR posts here several text files
; to be imported either as netmail or as echomail. Therefor, if you have
; a "secure" inbound for your mail tosser, use that one.
;============================================================================
INBOUND C:\MCM\INBOUND
;============================================================================
; NETMAIL defines the path to your *.MSG (="Matrix") messages.
;============================================================================
NETMAIL F:\SHRD\NETMAIX
;============================================================================
; HOMEPATH is the basic path where all xOR files and xOR Utilities are stored.
; Also, you key file must be placed there.
;============================================================================
HOMEPATH D:\TP\PRG\FIDO\XOR
;============================================================================
; PKTPath defines the temporary path where xOR creates pakets to be
; sent to other systems. Also, xOR creates here some temporary datas,
; so it is good NOT to share that path with other programs.
;============================================================================
PKTPATH D:\TEMP\XOR
;============================================================================
; DATABASE and the following statements define the path and name of xOR's
; file and path index bases in this way :
;
; DATABASE is the main database where the files are stored
; DESCBASE is the main database where the description indices
; are stored
; PATHBASE is the main database where the pathes are stored
; CDINDEX is the database where CD ROM file index are stored
; CDPATHINDEX is the database where CD ROM pathes are stored
; CDPATHBASE is the database where CD ROM description indices are stored
;
; CDBUFFER if enabled, xOR will copy all files requested from CDs to
; that path to speed up requests. That's very important
; if you run a multi-CD-ROM-drive, e.g. Pioneer 60?x changer
; NOTE : in multiline environments, the path is expanded to
; <PATH>.<TASK>, e.g. if TASK = 3, the path \TEMP\XOR.3 must
; exist on runtime!
;============================================================================
DATABASE D:\TEMP\XOR\DATABASE.FIL
DESCBASE D:\TEMP\XOR\DESCBASE.FIL
PATHBASE D:\TEMP\XOR\PATHBASE.FIL
CDINDEX D:\TEMP\XOR\DATABASE.CD
CDPATHINDEX D:\TEMP\XOR\PATHBASE.CD
CDDESCBASE D:\TEMP\XOR\DESCBASE.CD
CDBUFFER D:\TEMP\XOR
;============================================================================
; The following three statements represent statistical databases
;
; USERBASE is the user statistic base
; RESUMEINDEXPATH this is a PATH where resume files (*.RES) for each single
; user is stored
;============================================================================
USERBASE D:\TEMP\XOR\XOR.USR
RESUMEINDEXPATH D:\TEMP\XOR\RESUME
;============================================================================
; UseNetwareFeatures ON | OFF set to ON to enable special
; Novell Netware or compatible features (Personal Netware ect).
; This implies special treatement for Netware CAST messages ect.
;============================================================================
UseNetwareFeatures ON
;============================================================================
; SYSOP this is your native name on which the key file is coded.
;============================================================================
Sysop Mirko Mucko
;============================================================================
; The ALIAS files (also called "magic files") are defined now.
; You have two ways to include an alias, either by an alias list (an external
; text file) or by entering the alias here
;
; ALIASSFILE is the main alias index file
; ALIASDESCBASE is the alias description index file
;============================================================================
ALIASFILE D:\TEMP\XOR\ALIAS.IDX
ALIASDESCBASE D:\TEMP\XOR\ALIAS.DSC
;============================================================================
; To define a single alias instead of linking a text file, use that
; command. NOTE : "###" as extension forces xOR to search for the
; latest file matching the alias.
;============================================================================
ALIAS GERNODE D:\FILES\ALIASES\GERNODE.ZIP
ALIAS XOR D:\FILES\LOCAL\FRODO\XOR106.EXE
ALIAS LANFILES D:\FILES\ALIASES\LANFILES.ZIP
ALIAS *.* D:\FILES\Local\TEXTE\fuck_off.txt
;============================================================================
; xOR uses several different response text files to satisfy you and your user's
; needs.
;
; HEADER is the file linked to a response msg before the list of
; requested files
; FOOTER is the file linked to a response msg after all other
; HAPPY is a textfile sent when a user requests in a "happy hour"
; for explanation of HAPPY HOUR, RTFM .-)
; NOMAILER if enabled, xOR tries to deny all users using
; a mailer defined later on. This may run only in EMSI sessions
; NOREQNOW is a text file which explaines to users they are not allowed
; to request right now
; TOOSLOW is a text file sent when a user requests at a too low speed
; BREAKTIME is a text file sent when the limit defined with BREAKTIME exceeds
; FIRSTTIMETEXT is the text file a user receives the very first time he/she
; requests at your site. It may contain information about your
; system, baud rates, ports and request times
; DENYTWITTEXT is the text file sent whenever xOR assumes a user is a "twit",
; {+} a person which should not receive files from your system.
; These users are defined later on.
;
; QOD is the "quote of the day" file and optional.
; hee you define a file with one "joke" or nice sentence.
; per QOD, one line is allowed with up to 76 chars.
;
; Note that all files are without extension since the extension is defined
; by the AKA of the remote system (see your AKA definition above)
;============================================================================
HEADER D:\TP\PRG\FIDO\XOR\TXT\HEADER
FOOTER D:\TP\PRG\FIDO\XOR\TXT\FOOTER
HAPPY D:\TP\PRG\FIDO\XOR\TXT\HAPPY
NOMAILER D:\TP\PRG\FIDO\XOR\TXT\NOMAILER
NOREQNOW D:\TP\PRG\FIDO\XOR\TXT\SENDFAIL
TOOSLOWTEXT D:\TP\PRG\FIDO\XOR\TXT\TOOSLOW
BREAKTIMETEXT D:\TP\PRG\FIDO\XOR\TXT\BREAK
FIRSTTIMETEXT D:\TP\PRG\FIDO\XOR\TXT\FIRST
DENYTWITTEXT D:\TP\PRG\FIDO\XOR\TXT\NOTWIT
QOD D:\TP\PRG\FIDO\XOR\TXT\QOD
;============================================================================
; MinReqSpeed defines the minimal connection rate a user must have to have
; access to your filebase.
;============================================================================
MinReqSpeed 2400
;============================================================================
; The following commands define text fields sent in the response message
;
; NONEWERFOUND is sent when an time comparing request failed
; NOMATCHING is sent whenever the requested file is not found
; PSWDFAILURE is sent when a file is passwordprotected and the wrong
; password or none is entered
; TOOMUCHFILES is sent when a user exceeds it's limits by number
; TOOMUCHSIZE is sent when a user exceeds it's limit by size
; TIMEOUT is sent when a user exceeds it's limit by transfer time
; RTOOMUCHFILES is sent when a user exceeds it's limits by number per session
; RTOOMUCHSIZE is sent when a user exceeds it's limit by size per session
; RTIMEOUT is sent when a user exceeds it's limit by transfer time per session
;
; CDFILEREMOVED is sent when a requested file from CD is no more found
; FILEREMOVED is sent when a requested file is no more found
; DUPREQUEST is sent when a user requests one file twice or more
; for defining different levels of dupcheck, see later on
;============================================================================
NoNewerFound No file later than the required time found
NoMatching No matching file found
PswdFailure Password failure
TooMuchFiles Too much file numbers requested
TooMuchSize Too much file size requested
TimeOut Too less time left for this file
RTooMuchFiles Too much file numbers requested for one request
RTooMuchSize Too much file size requested for one request
RTimeOut Too less time left for this file for one request
NotReleased This File is not yet released. Try later!
CDFileRemoved CD no more presend, dismounted or changed!
FileRemoved File no more found, perhaps removed
DupRequest Duplicate file requested. Check your brain!
;============================================================================
; You may define different groups, to which you may refer later either
; in DEFINE statements and/or in password statements
; The first statement is the Group Name (case insensitive), the second
; is the AKA or one of the known keywords ("ALL","PROTECTED","UNPROTECTED", and
; "UNLISTED". The group name may have a maximum of 12 characters!
;============================================================================
USERGROUP All_User ALL
;============================================================================
; This defines a group of pathes. To add/remove a usergroup, you *must*
; re-compile all index files to take effect!
;============================================================================
PathGroup ALLFILES D:\
;============================================================================
; The Baud groups define how much files a user with a certain baud rate
; may get. So you may (but haven't to) seperate your friends with ISDN
; from the old webble ones with analog lines and low speed .-)
;============================================================================
BAUDGROUP ALLSPEED 300 1200 2400 4800 7200 9600 12000 14400 16800 19200 21600 24000 26400 28800 38400 64000
;============================================================================
; The most important part is the limit definition for your users.
; a definition line c onsists of 8 parameters
;
; 1 the line number in multiline environments or "0" for all lines
; and single line systems
; 2 the GROUP NAME defined by USERGROUP
; 3 the BAUD GROUP as defined above
; 4-6 the limits in minutes, number and kbytes per day
; 7-9 the limits in minutes, number and kbytes per request
;
; As an example, take that:
;
; DEFINE 0 ALL_USER ALLSPEED 60 30 1024 20 10 1024
;
; on all lines, unprotected systems may request
; 60 minutes, 30 files and 1 MByte per day and
; 20 minutes, 10 files and 1 MByte per request session
;
; The value "-1" means "unlimited", so you may limit requests e.g. only
; by time.
;============================================================================
DEFINE 0 ALL_USER ALLSPEED 5 5 128 5 5 128
;============================================================================
; The baud rates define the relation between a connect rate and a CPS rate
; If you don't specify all rates your mailer supports, xOR assumes a baud
; rate whenever an "unknown" baud rate appears. Note that baud rate for off
; line requests is defined by OLIBAUD.
;============================================================================
BAUD 1200 110
BAUD 2400 235
BAUD 4800 400
BAUD 7200 600
BAUD 9600 800
BAUD 12000 1100
BAUD 14400 1250
BAUD 16800 1450
BAUD 19200 2200
BAUD 38400 3500
BAUD 64000 7500
OLIBAUD 64000
;============================================================================
; In some text files, the days of week appear. Depending on your favourite
; language, you may adapt it to your needs.
;============================================================================
WEEKDAYS Sunday Monday Tuesday Wednesday Thursday Friday Saturday Everyday
RequestTime 0 0000 2359 ALL_USER All
;============================================================================
; For F I L E S . B B S style environments ONLY
; This section is read by FILESIDX only, not by xOR
; It defines the pathes & files to use when FILES.BBS is used.
;
; FILELIST <Level> <Path_&_File> defines the file with
; pathes to be included
; The structure of this file is one path per line, with or without
; trailing backslash.
; The first file sohl be your "default" list, the other one additional lists.
; Be sure at least one list is for all, and do not define pathes
; twice if possible since it make the index files grow up.
; Do *only* include "real" files on hard disk, not CD ROM devices
;============================================================================
FILELIST F:\SHRD\FILES\XFILES\FDOKFILE.LST
;============================================================================
; With the GRANT statement, you grant the access right(s) to special files
; to a special group of user.
;============================================================================
GRANT ALLFILES TO ALL_USER
;============================================================================
; E n d o f S i m p l e C o n f i g u r a t i o n f i l e
;============================================================================