I've noticed the same thing happening here. The MIS2.LOG takes awhile before it will update the information. I'm not sure if that's be design, or what...

It buffers the logs to minimize updates, but the system isn't that great at
the moment.

The reason it does this is to lessen the amount of writes to the log files
for systems like Pi which often run on SD cards.

I need to do more work on it so it more intelligently updates logs, like when
a major event happens (end of a session) or after a time interval where no logging has been updated.

The whole system needs reworked.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 08/23/17, g00r00 said the following...

I've noticed the same thing happening here. The MIS2.LOG takes awhile before it will update the information. I'm not sure if that's be desi or what...

It buffers the logs to minimize updates, but the system isn't that great at the moment.

I figured that is what it was doing. (either that, or you forgot to
fileclose() (just kidding, I know you wouldn't forget that) ;)

Thanks,


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A34 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)