Subj : MPL Question
To : g00r00
From : Black Panther
Date : Wed Apr 06 2022 12:14 am
Hello g00r00!
05 Apr 22 13:00, you wrote to me:
BP>> This is returning '0' to the log file when logging in from the
BP>> command line. I wonder if possibly adding a servertype for local
BP>> login might be simpler than doing the 'local' boolean. Perhaps
BP>> adding servertype of 3 for local.
gr> I don't know what OS or version you're using but it seems to be
gr> working from here I just tested it in Windows A48 and Linux. The
gr> simple test I did was logged in and tried to download the BBS list and
gr> on both OSes it says "Local mode:" and asked me to save.
My test system is running Manjaro Linux 64-bit, with Kernel 5.15.28-1-MANJARO x86_64.
Let me run a test using the bbs listing as see if that is any different.
gr> Are you sure you're logging in with -L? Make sure you're not setting
gr> the value of Local anywhere in any MPL anywhere, otherwise that will
gr> change it for the entire connection.
Yes, logging in either is -L or running the mpl from a command prompt with the './mystic -Uuser_Name -Ppassword -X'basicmpl test' format. Neither one will show the local as being true. Also, the variable is not being changed anywhere else in the code.
gr> The ServerType that is used internally by Mystic for terminal services
gr> does have a Local mode value. They should be (as of A48 current
gr> releases):
Ooooo. Didn't know about the others on here. So, when it's a local connection the servertype should also be showing as 4. Looks like I have some more playing to do. :)
