Subj : Re: ruling out
To   : Rick Smith
From : g00r00
Date : Sat Dec 31 2022 12:49 pm

 RS> I do not see anything in the logs.. The paths should be the same /mystic
 RS> I can now get mystic -cfg to work (turned out I did have a couple pi
 RS> executables remain qwkpoll and couple others, took care of that did a
 RS> whole fresh install on a new ubuntu machine.
 RS> 
 RS> now when I run ./mystic -l I simply get a blank screen that just says
 RS> "busy" and have to ctrl c to get prompt back. ./mis starts and runs and
 RS> appears fine.  Not sure what to check next to be honest.  I can start
 RS> another vm and try again but I am pretty sure thats the definition of
 RS> insanity! lol

That sounds like it could be access related and maybe a chown would help:

sudo chown -R bbsuser:bbsuser /mystic

You would replace "bbsuser" with whatever user/group that is running Mystic BBS.  If you don't know the user you can type "whoami" to see it and "groups" to see a list of groups you're in.  For example I login as "me" on my computer so it would be:

sudo chown -R me:me /mystic

You might also want to go into /mystic/data/ and "rm chat*.dat".  Afterwards do a "ls -la chat*.dat" to make sure there are no chat files left.

.... Unzip... expand... What kind of pervert came up with this?

--- Mystic BBS v1.12 A48 2022/12/30 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.