REPLY: 2:250/1@fidonet 61df2c85
MSGID: 2:250/1@fidonet 61df4760
CHRS: UTF-8 2
TZUTC: 0000
TID: MBSE-FIDO 1.0.7.24 (GNU/Linux-x86_64)
Hello Sean!

Got one more for you hopefully an easier one,

When running mbsetup have parameter does does NOT stop the system from
answering call/polls or making them - On the basis that the system not being
changed  but as back up protection if needed that any change about to be make
when in this mode that the system is put on pause as current and released 
after
a change (any change that effect the way the system works)

OR

just state that changes not permitted as mbsetup ruuning in system operating
mode or words that that effect.


I seem to be going into mbsetup just to look at setting such as aka's (7) to
see what nodes are the system and general type settings and not change a thing
as I am only looking say when writing a netmail.

Suggestion, that if setting this mode a flag is set that can be read by all
programs that refuses any changes with a error message OR pauses mbse
operations as at present until changes are made the mbsetup exits.
Its a screw up once, then it sticks to default until mbsetup exits.

Out of interest there a a number of settings that could be made with the 
system
fully operational but it would require going through them to see what fits 
that
scenario.


Vincent
--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
 * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
SEEN-BY: 1/123 14/0 15/0 18/200 25/0 21 30/0 90/1 103/705 105/81 106/201
SEEN-BY: 120/340 123/131 129/305 153/7715 154/10 218/700 221/1 6 226/30
SEEN-BY: 227/114 229/110 424 426 428 452 550 664 700 240/1120 5832
SEEN-BY: 249/206 317 400 250/0 1 2 3 4 5 6 7 8 10 21 263/0 266/512
SEEN-BY: 280/464 282/464 1038 292/854 301/0 1 101 113 317/3 320/219
SEEN-BY: 322/757 342/200 396/45 633/280 640/1321 712/848 920/1 3634/12
SEEN-BY: 5020/1042 5058/104
PATH: 250/1 301/1 229/426