Is there a list of Mystic semaphores anywhere? Sorry, but I did look ;) Specifically, I'm looking for a semaphore that would stop Mystic from opening or would tell it to close the .log files so that I can write to them
externally while the board is up.

Thanks in advance!

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (77:1/104)

Is there a list of Mystic semaphores anywhere? Sorry, but I did look ;) Specifically, I'm looking for a semaphore that would stop Mystic from opening or would tell it to close the .log files so that I can write to them externally while the board is up.

There is no semaphore to do that and I don't have any plans to add something like that.

What log do you want to write to and why? If its the node log you can do that with MPL, Python, or Menu commands. You can turn caching off mis log, poll log, and mutil too. But this is going to cause the file to open and close every time a line is added to it, which is not good for wear and tear on your disks.

--- Mystic BBS v1.12 A46 2020/05/11 (Windows/64)
* Origin: Sector 7 (77:1/138)

Hay g00r00!

Thanks very much for the response!

There is no semaphore to do that and I don't have any plans to add something like that.

Understood!

What log do you want to write to and why? If its the node log you can
do that with MPL, Python, or Menu commands. You can turn caching off
mis log, poll log, and mutil too. But this is going to cause the file
to open and close every time a line is added to it, which is not good
for wear and tear on your disks.

Actually, the problem I am having is that I am reading the mis.log file into
a program I am working on and I'm having file locking issues. THe program
runs fine if Mystic is down but it is probably my code so I'm looking for a workaround. Is there a way to shutdown Mystic in the event system by creating a semaphore event? If so, I could run it in a batchfile and branch back after I do my business.

This is not critical as I need to find out why the pascal program is unable to open mis.log for read. Thats the real fix but this query also helps me learn how Mystic operates. I do not find alot of documentation regarding semaphores. Perhaps thats because there are only four that Mystic
knows natively?

Thanks again for your response. It is ALWAYS appreciated!

.\\ichael Batts
a.k.a. stizzed (because, why not?)
SysOp, The ROCK BBS III

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: The ROCK BBS III - therockbbs.net - TELNET:10023 (77:1/104)

Actually, the problem I am having is that I am reading the mis.log file into a program I am working on and I'm having file locking issues. THe program runs fine if Mystic is down but it is probably my code so I'm looking for a workaround. Is there a way to shutdown Mystic in the
event system by creating a semaphore event? If so, I could run it in a batchfile and branch back after I do my business.

If you go into System Configuration > Logging you can turn caching off for mis.log. What that does is tells MIS will open and close the log for each
line it logs, so you should be able to open it while MIS is running.

The downside is that instead of keeping it open and writing chucks of logs at like 4kb at a time when its cached (to reduce disk activity), it will be writing each line one by one.

This was a feature I added relatively recently so it might only be in the A46 versions and not A45 (I can't quite remember for sure).

--- Mystic BBS v1.12 A46 2020/05/11 (Windows/64)
* Origin: Sector 7 (77:1/138)