On 06/05/16, Pequito said the following...

On 06/05/16, Mitch Greive said the following...

I noticed today that if i close mis down with no one online, nothing out of the regular, that it will create a .bsy file in the semaphore directory and cannot be restarted until this is deleted. anyone else having problems with this. just started after the last alpha upgrade

The .bsy file is created at launch not shutdown, sounds like you closed MIS the wrong way. With the window in focus his ESC and then YES to
close MIS.

This way should clear the .bsy file in the semaphore folder.

I have not upgraded to A17 yet. I'm still waiting for others to do the beta testing for me, since it appears that we could be rolling back. Also, the
bsy semaphores give me pause. I will now have to track them to see if my processes are failing or not. What happens if MIS is running in daemon mode, and it crashes? Will it clean out the bsy flag when it starts up? Or do I have to do it manually before it will start? There is no graceful way to
kill MIS in daemon mode; the only way to do it is to kill the process. That implies that MIS will not clean out the bsy flag. So when I do my upgrades,
I have to kill MIS first. Do I now have to start cleaning out the mis.bsy
flag each time?

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A16 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX

On 06/07/16, g00r00 said the following...

I have not upgraded to A17 yet. I'm still waiting for others to do t beta testing for me, since it appears that we could be rolling back.

Its been running FSXNET which is getting 500 posts per week, and of
course I run things for a while before released as an alpha. Why do you say it appears we could be rolling back?

Prolly because you specifically said it when you announced the release.

I haven't had to change anything so far, and I will not be reverting
back to the non-BSY file way.

to see if my processes are failing or not. What happens if MIS is running in daemon mode, and it crashes? Will it clean out the bsy fl

If it crashes you'll need to delete the .bsy file. Same with other mailers.

There is no graceful way to kill MIS in daemon mode; the only way to it is to kill the process. That implies that MIS will not clean out

That is not true unless its not working. MIS will shutdown gracefully when it receives a SIGTERM from Linux, which is how daemons are supposed to work.

See. I wasn't aware of that functionality. I did not know that MIS would
kill bsy flags when killed with SIGTERM.

bsy flag. So when I do my upgrades, I have to kill MIS first. Do I have to start cleaning out the mis.bsy flag each time?

Is typing "rm mis.bsy" during an upgrade (in a WORST case scenario)
really all that big of deal?

I have several scripts to call the various MUTIL functions. At least one script for every MUTIL function that I use. Each one will likely need to be checked. I could possibly miss some.

The amount of time it took you to type this message is probably more effort than it will take you to delete the .bsy file if needed during an upgrade from the next couple of years. :)

Upgrading for me isn't exactly a simple task. The reason for that is becuse
of all the MPL programs that I run. I run at least 50% more mpl apps on Cyberia than I have ever released to the public. Most of those are in their own separate directories. The MPLC -ALL function doesn't touch the MPLs
that are in directories other that the current /SCRIPTS dir. So I have to
run separate scripts just to have them all updated. Plus, I like to do a BBS backup before I do any updates.

I'm not complaining. I mention all this to show that upgrading is not a trivial matter for me.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A16 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX

On 06/08/16, g00r00 said the following...

Upgrading for me isn't exactly a simple task. The reason for that is becuse of all the MPL programs that I run. I run at least 50% more m apps on Cyberia than I have ever released to the public. Most of tho are in their own separate directories. The MPLC -ALL function doesn' touch the MPLs that are in directories other that the current /SCRIPT

You're going to be very pleased with A18's MPLC then! :)

Mystic BBS Programming Language Compiler Version 1.12 A18
Copyright (C) 1997-2016 By James Coyle. All Rights Reserved.

MPLC [path/file] : Compile one script [path/file]
MPLC -ALL : Compile all scripts in current dir and subdirectories MPLC -C : Compile all scripts in current directory
MPLC -P [path] : Compile all scripts in [path]
MPLC -R [path] : Compile all scripts in [path] and its subdirectories

Well cool! Thanks!

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A16 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX