Subj : Re: Follow-up on "Some A48 issues (summed up)" (as per 07/09/2022)
To   : g00r00
From : Bj”rn Wiberg
Date : Sat Jul 09 2022 02:53 pm

Hello again g00r00!

I hope you will forgive me for all my messages, as I really don't want to interrupt your work...

On 09 Jul 2022, Bj”rn Wiberg said the following...
 BW> I'll let you know if I would stumble across anything additional, but I

* I edited resetpw.ini and emailval.ini in the data directory (also tried copying to the theme's text directory), but it appears that Mystic doesn't use the INI files just yet? (I got the "old" hard-coded messages e-mailed
out.) Being able to customize those messages will be great!

* When copying (/C) and pasting (/P) an action to the action list of a menu command: If the command list is already full (25 entries), pasting will overwrite the highlighted action (if any -- one could be at the empty line below all actions, in which case nothing would happen). Perhaps the paste function could/should be greyed out of there isn't room for another action? And perhaps the empty line ("room for another action") at the bottom of the action list shouldn't be shown if the list is full?

* I have Disable Time: No and a security level (s255) which has Time Per Day: 9999. Do Shell events with Warning: x (minutes) really kick the user out? I would expect Mystic to trim the available time (9999 minutes) down so that the closest event with a Warning value set will be able launch without any users being logged in. But it appears that I get 9999 minutes per day and don't get kicked out during the events with a Warning value.

For what kind of events does the Warning value affect the amount of remaining time?
Did I perhaps ruin something by setting the Time Per Day to > 1440 minutes?

Background: I'm using the Shell event type (and not a "BBS" type event) for my daily/weekly maintenance events since I do not want MIS to exit (it is started via systemd and I want it to be running, but without users logged on).

I do create/remove a semaphore of my own during/after the maintenance, and check for that during logon, so that any attempts to log on during maintenance will honor the ongoing event. But it is more of a work-around as I do not know of any built-in semaphore of Mystic to prevent logins.

(And for a SysOp account, one might want to be able to override this in case something goes wrong, one is at a remote location, and needs to e.g. remove the semaphore via a menu command or the Mystic-DOS Shell...)

Thanks in avance!

Best regards
Bj”rn

--- Mystic BBS v1.12 A48 2022/07/07 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

.