DP Tool Club 8/CDASC08.ISO/VRAC/TUSERP41.ZIP/TOPUSERS.DOC

Text File | 1992-12-24 | 4KB | 91 lines

Welcome to TOPUSERS version 4.0!

Created by Erik VanRiper 1:107/230

Usage:
          TUSERSP [config_file]

Example:
          TUSERSP

Or:

          TUSERSP topusers.cfg

Run it whenever you wish, I run it during my midnight maintenence.  It is
fast enough to run each time a user logs off if you really want to be up to
date.

I use a:

[Display_File]Misc\Topusers

to show it off on my Bulletins menu.

This version will handle up to 4000 users!  (untested at that many users,
but what the heck.  That is what support is for!)

The configuration file must be edited to suit your system and color
preferences, as well as style of lines and number of "top" users.
Everything in TOPUSERS.MEC is explained, with one outside reference: the
ColorVacant command.  Vacant is the word I chose to use when there is no
user that can fit in the list, such as a system with few files, there may
not be 10 people (or 100) that have uploaded anything.  So, instead of
placing someones name there, a "----- Vacant! -----" is placed there
instead.

The SysOp keyword warrants a bit of explaination as well.  If you include
this keyword, then the SysOp (user 0) will be included in the output
listing. Including all of the SysOps calls/ups/downs in the total fields at
the end of the listing.  If this keyword is commented out, then the SysOps
totals are not included, giving a more realistic value to each column.

The totals at the end of the display are for ALL users in your user file,
not just the top ten, and with the noted exception above.

THE IMPORTANT THING TO REMEMBER about the configuration file is that there
is only one space between the key words adnd their arguments (if any).  The
reason for this is because Mecca's RLE will make the spaces shrink, and add
characters to the actual argument as it is compiled.

If you started your system as a single line, then put up more nodes, you
will probably want to also include node number 0 as well.  I have found
that when MAX goes multi-line, it will copy BBSTAT00.BBS to BBSTAT01.BBS,
then create empty ones for each node after that.  HOWEVER, then only info
that is properly transfered is the number of callers, NOT the DL's, UL's
and messages posted. So, what I did was used the EDITCALL utility that came
with Maximus, and edited to BBSTAT00.BBS file to a decent number of calls,
and use 0, 1, 2, and 3 (3 is my local node, 1 and 2 are my public nodes,
and 0 was the old public node before going multi line) in the TOPUSERS.CFG
file.

You can have as many configuration files as you want, allowing you to
create many different lists.  The default configuration file name is
TOPUSERS.CFG, found in the same directory that TOPUSERS is run from.

Users with the "Do not list me in the userlist" flag will not be displayed
in the output listing.

I think I have added everything that I can think of in terms of being able
to have control over the output, if you can think of anything else please
let me know.

Questions?  Comments?  Suggestions for Version 5.0?  Send 'em NetMail, or
contact me through the Maximus support conference MUFFIN.

Source code available on request.  It was written in C, and I used
Borland's TC++ 1.0 compiler in the normal C mode.

Special thanks to:

 Carl Slawinski of the Buccaneer's Harbor BBS ([phone])
 Janis Kracht of the <<PRISM BBS ([phone])
 Noel Smith of the Cave in the Woods BBS ([phone])
 Don Dawson of the Treasure Island BBS ([phone])
 Dave Morhun of the Peace of Mind BBS ([phone])

And Ray Gardner for his qsort routine "A version of qsort that uses Shell's
sort algorithm." dated 11/91 and placed in the public domain.

/* Erik */