On 29 May 2024 at 10:12p, g00r00 pondered and said...
g0> This shoud be fixed in the latest prealpha build but still would of
g0> course be mostly untested.
Hi there.
Just a note that I tried the 32bit RPi build installer and it failed to allow me
to install to /mystic/ from the root directory. I tried the sudo ./install
option and that did not work either. Just hit the unable to create /mystic/
message.
If I opted for F5 use home directory it showed me the root path of /root/mystic
so I can confirm I was acting with root privileges when I invoked sudo but hit
the above mentioned problem.
Also during an earlier test on the last 64 bit build I found I was having
problems using 'mis poll 21:1/100' when I set up 21:1/100 as a BinkP echomail
node in Mystic.
For whatever reason it looked like mis was polling out to the BinkP server but
the receiving system on another machine on my LAN did not see any incoming
connection from MIS on the Rpi..
So just flagging there *may* be something in the Rpi code that *might* be amiss
when 'mis poll' is calling a binkP style echomail node?
Another thing I spotted in the mutil.ini there's a reference in whatsnew.txt to
the new function EchoUnlink.
; exclude=MYSTIC
; exclude=FSX_*
But the reason I mention this because I wanted to let you know that you've
omitted the function call at the top of the mutil.ini
; EchoUnlink = false
[time passes]
I also ran a test using the exclude=FSX_* but have found it does not honour the
switch, the reports I am generating 'action_mode=0' are still flagging fsxNet
bases that should be excluded. So something is may be up there also.
I ran the function from mutil directly using ./mutil -run EcoUnlink
Best, Paul
Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going'
avon[at]bbs.nz | bbs.nz | fsxnet.nz
--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
|
