Subj : Re: How Linux and Windows installs differ
To   : McDoob
From : Zip
Date : Wed Dec 15 2021 09:28 pm

Hello McDoob!

On 14 Dec 2021, McDoob said the following...
 Mc> It took me entirely too long to figure out why my events were failing!
 Mc> And it all came down to exactly two characters in the command line: "./"

Ah, yes, that one sounds familiar. :-D

 Mc> Recently, I've gotten into the (bad) habit of accessing Mystic config
 Mc> from the SysOp menu. I tried several times to update my events after

I also do that -- usually I connect "locally" to the BBS using a Telnet/SSH terminal program (SyncTERM) and then launch the System Configuration from the SysOp menu.

This has the advantage of character encodings being "correct" (CP437) which might be important if you need to be able to edit e.g. message base descriptions with "special" characters in them.

 Mc> figuring out the above difference. And there began my second "D'oh!"
 Mc> moment...because McDoob is not a user in the linux OS. Therefore, McDoob
 Mc> did not have permission to alter the event configs!

I do change event configs from within the BBS, however MIS needs to be restarted for any event changes to take effect.

Of course, editing events requires the data/events.dat file to be writable by the Linux user that the BBS is running as. The latter probably has a (Linux) username completely different from that of your BBS user account inside Mystic.

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/12/13 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.