home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
DAYSTS15.ZIP
/
WHAT'S.NEW
< prev
Wrap
Text File
|
1992-10-02
|
2KB
|
40 lines
With revision 1.5 of DAYSTATS, one potentially major bug was fixed and
a saftey feature was added.
THE BUG FIX:
If your BBS was multi-Node and you didn't run your node
numbers consecutively, ( i.e., you numbered 1-9 then
skipped to 15,) then Daystats had the potential
to improperly record the node numbers, which would lead
to extra lines in the bulletin usually with no stats
information and the date would be something in the year
1979.
If your BBS had this problem, then this new code will
correct that. YOU WILL HOWEVER, Need to RESTART your
DAYSTATS.DAT file from scratch. Essentially all you will
need to do is delete DAYSTATS.DAT. The next time Daystats
runs, it will create a new one for you.
ADDED FEATURE:
I neglected to think about these multi-node BBS's which
don't shut down all nodes of their BBS to run the event.
This of course meant that there was a chance that someone
could be reading your STAT bulletin at the very precise
moment that you wanted to create the new one. In a network
environment, this could create a lock on the file where
DAYSTATS wouldn't be able to update the file. Previously
the program would simply abort cleanly and leave the
temporary file in the calling directory.
New code has been added which will try for 2 minutes to
create the new bulletin. Every 15 seconds for up to 8 times,
DAYSTATS will attempt to write the new file. If the file
cannot be created in 8 tries, it will exit the program,
leaving the DAYSTATS.TMP file in the calling directory.
You can manually copy the .TMP file to the bulletin later
if necessary. No loss of stats data will occur because of
this. The next time DAYSTATS runs, it will create a new
bulletin, including the data from the previously
unsuccessful run.