home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Black Box 4
/
BlackBox.cdr
/
bbs_opus
/
util170.arj
/
OFARE.DOC
< prev
next >
Wrap
Text File
|
1991-07-11
|
4KB
|
91 lines
OFARE
Opus 1.70 File Area REindexer
The purpose of this program is to re-index the database. When Opus
adds new files to an area, the information for that file is added
to the "overflow area" of the database. When a file is deleted, the
entry in the database is not physically purged, it is just marked
as deleted. Opus doesn't even expand wildcard names that occur in
a file area anymore, because you can't put wildcard names in a file
index.
In order to purge deleted files from the database, combine the
information from the "overflow area", and to re-expand wildcard
names, OFARE should be part of your regular maintenance. Of course
Opus-FAM will also re-index the database.
If your filesbbs.ndx or filesbbs.adx files are grunged or lost, ofare
has the capability of re-creating them. If you loose the filesbbs.dat
file, too bad, you're in for a painful process. Backup frequently!
allowable command line switches are:
/o include orphan files
/m exclude missing files
/q quick mode (don't update file date/time/size)
Since Opus 1.70 allows the system dat files and the user file to be
located in other than the Opus home directory, support has been added
to look up these paths in the Opus prm file.
Set up an environment variable labelled OPUS, and specify
the full pathname of the prm file, i.e.
SET OPUS=H:\OP170\BBS.PRM (if your environment space is cramped,
you may leave off the .PRM suffix, the program will add it).
BTW, Doug and I are making the OPUS environment variable
a standard for all the OPUS utilities. If you want the C source,
just ask.
If the OPUS environment variable is not set, the program will look
in the current working directory for USER.DAT and SYSMSG.DAT. If
either file is not found, it will then look for BBS.PRM and look
up the paths in there. If none of the above are found, the program
will fail.
HOW TO CHANGE AREA NUMBERS (without losing a thing)
==========================
What do you do when you want to move a file area to a different area
number? For example you want to make your current games files area
which is currently area 15 into area 88. First run uncon to take all
the file descriptions for area 15 from the database and create an
old style files.bbs file. Then edit your bbs.ctl file, changing file
area 15 to file area 88. Run nacl which will create a new sysfile.dat.
Then run ofare, which will see that area 15 has been deleted, and that
area 88 is a new area, so it will merge the files.bbs for area 88 back
into the database.
John Valentyn 1:114/5@fidonet.org
Revision history:
ver 9 2-27-91
Added code to detect bad ptr left by Opus when it aborts while
adding new files.
ver 10 3-17-91
Fixed problem handing deleted record ptrs in overflow area.
Changed logic so that the new database is built as temp files, leaving
the old database and backup files intact in case Ofare aborts.
ver 11 3-26-91
Supports new _numb_idx structure.
Carries uploader name/date and download counts forward on wildcard files.
ver 14 5-4-91
Fixes some minor problems when adding new area(s).
ver 15 6-16-91
Fixes problem when the file areas in sysfile.dat are not in ascending
numerical sequence.
Somewhat speeded up disk i/o.
ver 16 7-4-91
Some more fine tuning to speed it up.
Fixed problem with priv levs in filesbbs.adx.
ver 17 7-9-91
Fixed problem that reported FILESBBS.NDX not found, and aborting, instead
of automatically rebuilding the file.
Added code that will set the upload date/time to the file date/time if
the file date/time is later than the upload date/time.