Hello There,

Since doing a fresh install of Mystic v1.12 A35 L64b I have noticed that when
I try to load the Mystic Mail reader by executing "./mystic -u<Username> -p<Password> -xmailread" in a terminal window.

I get the following:
-------------------
myst@bbbs1:~/mystic$ ./mystic -u<Username> -p<Password> -xmailread
<something that can't be displayed in this message> (U
BSY


myst@bbbs1:~/mystic$
-------------------

I recompiled all the scripts and still get the same response. If I use
command lines of:

./mystic -u<Username> -p<Password> Same response

./mystic -u<Username> Same response

./mystic Same response

I became aware that if I have the telnet nodes set to 1 in Mystic config THEN
I get the above behavior. If however I set the telnet nodes to 2 or more then the above Mystic mail reader commandline loads fine.

Just an observation.


Jeff

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: The OuijaBoard Too - Anoka, MN USA (21:1/128.1)

On 10/11/17, Jeffs said the following...

Since doing a fresh install of Mystic v1.12 A35 L64b I have noticed that when I try to load the Mystic Mail reader by executing "./mystic -u<Username> -p<Password> -xmailread" in a terminal window.

I became aware that if I have the telnet nodes set to 1 in Mystic config THEN I get the above behavior. If however I set the telnet nodes to 2 or more then the above Mystic mail reader commandline loads fine.

Yup, that makes sense, likely why the default is 4 nodes ;) I guess UBSY
isn't the best error message, my guess it means the one node is tied up (hacking?). Was there a reason to close it down to one node? Should likely do no less than 2 nodes so sysop can 'snoop' ;)

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Workpoint (21:1/145.3)

Hello bcw142,

I became aware that if I have the telnet nodes set to 1 in Mystic config
THEN I get the above behavior. If however I set the telnet nodes to 2 or
more then the above Mystic mail reader commandline loads fine.

Yup, that makes sense, likely why the default is 4 nodes ;) I guess UBSY isn't the best error message, my guess it means the one node is tied up (hacking?).

I currently have the node setting set to three. The system currently is for testing and therefor is open to trying different system settings.

Was there a reason to close it down to one node? Should likely do
no less than 2 nodes so sysop can 'snoop' ;)

Not really. Just checking program behavior using different config settings. I tend to be curious as to what effects changing a setting has on overall system behavior.


Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)