home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_ra
/
postlgra.arj
/
POSTLOG.DOC
next >
Wrap
Text File
|
1991-03-10
|
5KB
|
199 lines
┌─────────────────────────────┐
│ -*- Postlog-RA -*- │
└─────────────────────────────┘
v1.00
For RemoteAccess v1.00+
by
Bob Ransom
Copyright (c) 1991
All Rights Reserved
Postlog - What It Is -
--------------------
Postlog is a little utility that will scan your
RemoteAccess system log for any messages that have been
posted, and keep a running total of how many have been
posted to each message area. With this information,
you'll have a better idea of which of your message areas
are actually being used.
Postlog - How To Use It -
-----------------------
Postlog can be run from anyplace on your hard drive(s) and
requires one command line parameter. A second command
line parameter is optional. Syntax:
Postlog <system log filename> [<-Opus>]
The first parameter is your RA system log name (most often
RA.LOG). You may optionally include a full path here or,
if you use the logfile name only, Postlog defaults to the
current director. No checking of the RA environment
variable is done.
The second parameter is "-Opus" (case is unimportant).
This denotes that you're using Opus-style system logs.
Postlog defaults to using FrontDoor-style logs and will do
so unless it finds "-Opus" as the *second* command line
parameter.
Here are a couple of working examples:
POSTLOG ra.log ;ra.log in current dir and
;FD logs.
Postlog-RA v1.00 Docs Page 1
POSTLOG c:\ra\ra.log -opus ;ra.log in c:\ra. Opus logs.
Postlog - What's Written To Disk -
--------------------------------
When run, Postlog does it's stuff and shows the results on
the screen. It also writes two files to disk:
Postlog.ASC, a text file suitable for BBS display showing
the same info as shown on screen, and Postlog.CTL, a
control file used internally by Postlog to keep track of
things as time goes by. You may want to put Postlog.ASC
into your BBS textfiles area to be displayed as a bulletin
on your system.
Postlog - Misc. -
---------------
You can run Postlog on the same log over and over again if
you wish. It uses a sort of "last processed" pointer in
the .CTL file to determine which lines of a log have been
processed and which haven't.
Postlog will probably become confused if you switch log
types in mid-stream. If you do want to switch, I'd
suggest at least deleting the existing system log before
running Postlog again. It may or may not be a bad idea to
kill the Postlog.CTL file, too.
Postlog will also become confused if run it with the wrong
type of log - i.e. set for FD logs but run on an Opus log,
and vice versa. Your results will probably be extremely
weird.
For those of you with good memories, yes, Postlog existed
(still exists, actually) as a QuickBBS utility. This
version, however, is strictly for RemoteAccess because of
system log differences between the two systems.
Postlog - Legal -
---------------
Very little to say here except that Postlog is mine -- I
wrote it and I own it, but you may use it all you'd like
for free. You may copy it and you may give it away, but
you may not sell it nor change it or its documentation
(this file).
Postlog - Support -
-----------------
Postlog-RA v1.00 Docs Page 2
I doubt there's much call for support given the extreme
complexity of the program. <grin>
Seriously, if you have problems with it, please let me
know. I'm available via netmail (address below) or
through the RA_SUPPORT and RA_UTIL echoes.
Hope you find it useful.
-Bob Ransom
The Creative Connection BBS
Southfield, Michigan
(313) 559-9039
1:120/96.0