home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 1
/
crawlyvol1.bin
/
bbs
/
citadel2
/
util.doc
< prev
next >
Wrap
Text File
|
1989-12-01
|
17KB
|
340 lines
/************************************************************************/
/* Util.doc */
/************************************************************************/
/************************************************************************/
/* Audience */
/* */
/* Sysop and other troll-like folk. */
/************************************************************************/
/************************************************************************/
/* Purpose */
/* */
/* Let the poor unfortunates be even more confused over what's */
/* available. */
/************************************************************************/
/************************************************************************/
/* Contents */
/* */
/* Introduction Intro to this doc. */
/* Clog.ttp Description of Clog. */
/* Recover1.ttp Description of Recover1. */
/* Ctdlchng.ttp Description of Ctdlchng. */
/* Lexpand.ttp Description of Lexpand. */
/* Logedit.ttp Description of Logedit. */
/* Popular.ttp Description of Popular. */
/* Citar.ttp Description of Citar. */
/* Citsh.ttp Description of Citsh. */
/************************************************************************/
/************************************************************************/
/* Introduction */
/************************************************************************/
Since the days of yore when we received Citadel (the Z80 version of
Citadel, that is...) from CUG (C User's Group), several utilities of interest
have been added to the package to supplement the original two .com files that
came with the package, to wit CITADEL.COM and CONFIGUR.COM. These come in two
types: one, to provide information about what's going on inside this monster
which, due to runtime space considerations, could not be gotten at; two, the
ability to change certain parameters which were either impossible to change
once a BBS was set up, or were, at the least, difficult to change.
The descriptions (such as they are) follow herein!
/************************************************************************/
/* Clog.ttp */
/************************************************************************/
Clog provides access to the userlog for the Sysop. To use it, the file
CTDLTABL.SYS (the one generated by CONFIGUR and maintained by CITADEL.COM)
must be on the default disk, and so must be CTDLLOG.SYS.
There are two ways of using Clog. First, there is the simple call:
D>CLOG
This will print out on the console the list of users in the file as they
appear in the file. The user of this program should be warned that Citadel
does not put new users into the userlog in sequential order. Instead, they
are hashed into the log. Usually, first user to log into the system ends
up occupying the last position in the file! In general, users are sprinkled
everywhere, so don't be alarmed if nothing shows up right away. Be patient.
In any case, the list is printed out as follows. First, the log position
will be printed out, which will always be in sequential order. If nobody
occupies that position, then Clog proceeds to the next log position. If
somebody does occupy that position, then the name of that person (or alias)
will be printed out, followed by his/her status as aide, expert/non-expert, and
screen width.
The second way to use Clog is to give it arguments. There are two arguments
currently available in the GEMDOS version; the -p argument and the -a argument.
D>clog -p -a
-p will cause the passwords to be listed along with the user's name. This
is very useful if somebody forgets their password. -a will only list the aides
on the system (this was put in because some unscrupulous users might make
themselves aides if they get access to the system console).
If, for some reason, the sysop wants a list to be put out to a file, use
the GEMDOS re-direction commands. If you want the list to be put out to the
file LOG.LST, the type
D>CLOG >LOG.LST
Naturally, arguments may still be used when re-directing output.
/************************************************************************/
/* Expand.ttp */
/************************************************************************/
Expand's purpose in life is to allow the sysop to expand the size of his/her
message file (CTDLMSG.SYS). This makes it easy to move upwards as one gets
rich running Citadel for cold, hard cash and acquires better and better
equipment.
Expand expects to find the file CTDLTABL.SYS on the default disk in the
default user area and the CTDLMSG.SYS file on MSGDISK. Simply call Expand
without arguments. Once it has loaded CTDLTABL.SYS, it will display the
current size (in internal sectors, not* kbytes) of the message file, and
then ask for the new size. Answer in sectors, in decimal (unlike
CTDLCNFG.SYS -- remember when changing CTDLCNFG.SYS to accomodate the new
message size to change the number back to hex). Now Expand will do it's job.
THIS IS A SLOW PROCESS. Be patient. The program will be printing some stuff
out that might allow the sysop to figure out where the program is.
Once the program is done, it will say so, and will also tell you that
there is no reason to reconfigure. This is not* true -- the current version
diddles something in CTDLTABL.SYS which vapes the userlog, so you must*
reconfigure to keep the userlog valid.
IF you are changing the value of MSGDISK, which would usually merit a
reconfigure (groan), please see the section of this doc covering the
program called Ctdlchng.ttp. This should be of help to you.
/************************************************************************/
/* Ctdlchng.ttp */
/************************************************************************/
The purpose of Ctdlchng.ttp is to allow the sysop to change certain of
the parameters present in CTDLCNFG.SYS to a different value without going
thru the entire reconfiguration process one more time. Ctdlchng expects to
find CTDLTABL.SYS on the default disk and directory.
To use this program, ctdlchng may be called with 0 or more arguments. If
it is called with 0 arguments, the program prints on the sysop's console an
explanation of Ctdlchng's purpose and it's argument usage and returns the
sysop to GEMDOS. If 1 or more arguments are present, then each argument is
processed. Each argument on the command line should be separated by a space.
The user of this program will note that in the following list of supported
arguments, all derive straight from CTDLCNFG.SYS parameters.
There are two types of arguments possible, one to change a "boolean" value,
and one to change a "numerical" value.
To change a boolean value, merely type its name as an argument to Ctdlchng.
The value of that boolean will then be "flipped" to its opposite value. The
list of boolean arguments supported is as follows:
ROOMOK -- Is it ok for ordinary folk to create rooms?
ENTEROK -- Is it ok for unlogged folk to enter messages?
READOK -- Is it ok for unlogged folk to read messages?
LOGINOK -- Can unlogged people make their own logins? (Is system private?)
CLOCK -- Does system have a clock?
ALLMAIL -- Can everybody send mail, or only aides?
SEARCHBAUD -- Should the system do an auto search for 300 or 1200 callers?
(SPECIAL NOTE: If you are changing SEARCHBAUD from 0 to 1
and never wrote the SET300 and SET1200 routines, then don't
bother to use Ctdlchng.ttp. You'll have to go into
CTDLCNFG.SYS, write up those two routines, and then run
CONFG.COM so that those two routines are in CTDLTABL.SYS.)
TIMEOUT -- Do you want the system to take itself down in x (HOUROUT)
hours?
MIRRORMSG -- Do you want two message files functioning, one for writing
only, the other for both? This is for RAM disk operations.
NETWORK -- Wanna be part of the network?
LONG-HAUL -- Wanna be part of the national/long distance network?
So, if the sysop had originally configured with ALLMAIL set to 0, i.e., s/he
didn't want ordinary users to have access to the mail, and now has decided to
allow all access to the mail, the sysop would type
A>d:ctdlchng allmail
and the value would be flipped. More than one of the above could be entered on
the command line.
To change a numerical value, the sysop types the name of the numerical
variable, followed immediately by an '=x', where x is an integer. NOTE THAT
X MUST BE A DECIMAL NUMBER, UNLIKE THE CTDLCNFG.SYS FILE!!!! Also note that
when changing CTDLCNFG.SYS, remember to convert back to hex. Yah, it's a pain
in the neck. The reason CTDLCNFG.SYS must be changed is that the next time
Citadel crashes (whether it be a software or hardware crash), you don't want
to reconfigure with the old values still present. ALSO, THERE CAN BE NO SPACES
BETWEEN THE VARIABLE NAME, THE EQUAL SIGN, AND THE INTEGER, OR CTDLCHNG.EXE
WILL BE HORRIBLY, HORRIBLY CONFUSED. The list of supported numerical values
is as follows:
MSGDISK -- Disk the message disk is on (A:=0, B:=1, ...).
HOMEDISK -- Disk where all .HLP, .BLB, and .MNU file are kept.
SYSDISK -- Disk where CTDLLOG.SYS and CTDLROOM.SYS are kept.
NETDISK -- Disk where all net files (.ML and CTDLNET.SYS) are kept.
HOUROUT -- If TIMEOUT is TRUE, then this determines how many hours before
system comes down after being brought up.
MSG2DISK -- If MIRRORMSG is TRUE, then this determines where the file for
write-only is kept.
DAYDIV -- For networking. Determines on what days the networker goes
into operation. WARNING: This value should only be changed in
conjunction with the rest of the network.
NETLENGTH -- For networking. Determines how long networking lasts. WARNING:
This value should only be changed in conjunction with the rest
of the network.
SYSBAUD -- If installing new modem with differing bauds. Currently,
0=300, 1=300/1200, 2=300/1200/2400.
So, to change the baud rate your modem is running at, type
A>d:ctdlchng SYSBAUD=2
or whatever the new baud rate is.
Numerical and boolean variable changes may be mixed as the sysop pleases.
/************************************************************************/
/* Lexpand.ttp */
/************************************************************************/
The LEXPAND utility allows the sysop to expand his log beyond the
size selected for when the system was originally configured. This program
does NOT destroy the log file, it merely enlarges it.
Usage: Make sure that the log file is in it's usual drive. Call
Lexpand. After some grinding, it'll state the old size and ask for the
new size. Give it the new size, and sit back. It'll announce when it is
done and remind you to modify CTDLCNFG.SYS accordingly.
/************************************************************************/
/* Logedit.ttp */
/************************************************************************/
LOGEDIT is provided for when strange things start happening in the
log file, such as duplicate or semi-duplicate logs start appearing.
LOGEDIT allows any account to be killed purely by account# (position
in the log).
To run, make sure the disk(s) with the HOMEDISK and SYSDISK files are
in their normal positions, and run LOGEDIT. After some grinding, the
system will ask you what account you want to kill. Give it the number, it
will display name and pwd, and ask for confirmation. If you answer yes,
then the account will be killed. It will then ask for an account to kill
again. When finished killing accounts, answer this prompt with the number
it should provide.
/************************************************************************/
/* Popular.ttp */
/************************************************************************/
The POPULAR utility is a statistics-gathering utility, and, as such,
can be easily viewed as your basic feeping creaturism. However, for those
of us who have somehow acquired that horrible taste for odd statistics about
how people use Citadel, it does serve some purpose.
POPULAR gathers statistics about the Public rooms on a system. These
statistics consist of simply calculating how many people have forgotten
each Public room on a system. Yes, a rather odd statistic to gather, but
there it is. Once it has finished processing the data, it displays the
results in tabular form, in (roughly) the following form:
<room name> <# of people who have forgotten this room> <% of total users>
To use this utility, simply make sure your data files are in their normal
drives, and run this program. The output of this program may be redirected
to a file via the GEMDOS ">" directive, although not all the output will end
up in the output file. Unimportant output will continue to go to the screen;
the important data will end up in the file you designated.
There is one command line option available, "-m". If this option is on
the command line to Popular, it will also scan the message file, counting
the number of messages that originated in each room, and display that value
for each public room in the same tabular format.
/************************************************************************/
/* Citar.ttp */
/************************************************************************/
Citar was made up to copy files to and from Citadel directory rooms, adding
or deleting the file descriptions as it goes. If you want to copy a file
into a Citadel directory, type
CITAR <FILE> <CITADEL-FILE>
and enter a one line description of the file at the Comment? prompt. (the
file nnames must be the full pathname -- you can't just specify the
destination directory. If you are copying BLEH.ARC to the Citadel directory
FOO, you would type
CITAR BLEH.ARC FOO\BLEH.ARC)
To copy a file out of a Citadel directory, you type
CITAR -X <CITADEL-FILE> <FILE>
To read the desciptive tags on one or more files in a Citadel directory,
type
CITAR -V <FILE-1> <FILE-2> .... <FILE-N>
Finally, if you have more than one file you want to copy into or out of
a directory room, you may use citar in batch mode. To use batch mode, type
CITAR @<BATCH-FILE>
where BATCH-FILE is set up as a bunch of one-line entries like
<cmd> <from-file> <to-file> [comment]
The <cmd> is either 'a' to add files to the Citadel directory (if you
are adding files to the Citadel directory, you must* provide a comment,)
'x' to copy files from the Citadel directory, or 'v' to view the description
of the file. For example, if you want to copy F1, F2, ..., FN into the
Citadel directory STUFF and Q1,Q2,...,QN out of STUFF into the current
directory, you'd make up a batch file like this:
a F1 STUFF\F1 Comments for F1
a F2 STUFF\F2 Comments for F2
.
.
.
a FN STUFF\FN Comments for FN
x STUFF\Q1 Q1
x STUFF\Q2 Q2
.
.
.
x STUFF\QN QN
If the batch file was called DOIT, you'd type CITAR @DOIT.
NOTE: If you are running from the desktop, don't type the CITAR part when the
TTP parameters window pops up.
NOTE2: If you are copying into a Citadel directory, CITAR will prompt
you before you overwrite anything, but if you are copying out of a Citadel
directory, CITAR will silently overwrite things. BEWARE!
/************************************************************************/
/* Citsh.ttp */
/************************************************************************/
Citsh was made up for people who are running Citadel on a ramdisk and wish
to have regular backups made. Instead of running Citadel, you run Citsh --
whenever Citadel exits, the log, room, and message files will be backed up
onto the current directory. (And, when Citsh starts, it will copy those three
files from the current directory to their appropriate drives.) If Citsh
cannot find CTDLTABL.SYS, it will run CONFIGUR.TOS and inform Citadel that
it had to reconstruct the tables.
If you pass any arguments to Citsh, it will assume that the various
system files are already loaded onto their respective disks and not* try to
load them itself. If Citsh has anything go wrong with it, it will print out
a error message and exit.
This is particularly useful when run in conjunction with timeouts.