Hello Alan!

Sunday May 03 2015 21:07, you wrote to Andrew Leary:

 > Another concern I had with MBSE is that (when I ran MBSE) I spent a
 > lot of time in mbsetup, mostly just correcting typos or just looking
 > things over. When I entered certain areas of mbsetup the status in the
 > upper right corner would change to busy or closed even if I was just
 > looking around. I think it would be better if MBSE just reread it's
 > config if and when it needs to do that rather than closing the BBS and
 > mailer down when I am probably just looking around the config.

 > That's just my $0.02. :)

The reason why mbse stops or closes is to prevent any issues with users/sysops
coming through while the system parameters data files etc are being updated.

It has no way of knowing if you are just looking and treats all as possible
changes.

While I have never looked in detail I cannot say I have noticed it doing that
in any area of non-importance assuming there is any!

Mbse does not support multi node functioning as in having multi copyies 
running
useing the same databases in different VM's running it.

When I was running in that instance I cheated by building the mbse data areas
on and for each load but this was not for mail/file processing as that was 
held
until a user/mail session ended.

I have at least for the moment stopped doing it this way as since I have
switched to a boot SSD drive I have not seen a performance/security reason to
do so but that could always change as I am considering moving mbse processing
to Z/OS unix but for that its really me just playing around and use Z/OS
normally doing big iron stuff on smaller iron.

Well got to find some things for keeping me busy now that I am retired !

Vince

--- Mageia Linux v4/Mbse v1.0.4/GoldED+/LNX 1.1.5-b20130910