TID: Mystic BBS 1.12 A48
MSGID: 2:201/137 fc076fa8
TZUTC: 0200
Hello g00r00!
Thank you for your message!
On 11 Jul 2022, g00r00 said the following...
g0> BW> * I edited resetpw.ini and emailval.ini in the data directory (also t
g0> BW> copying to the theme's text directory), but it appears that Mystic
g0> BW> doesn't use the INI files just yet? (I got the "old" hard-coded messa
g0> Its supposed to be working.
I checked with strace, and it appears that it only checks the text directory
of the theme and that of the fallback theme (in my case, the "default" theme)
for the INI file, but not the "global" data directory (/home/bbs
mystic/data/resetpw.ini):
write(1, "\33[0;1;30m\33[0;1;33mSending password reset e-mail... \33[?25l",
57) = 57
access("/home/bbs/mystic/themes/scbbs_en/text/resetpw.ini", F_OK) = -1 ENOENT
(No such file or directory)
access("/home/bbs/mystic/themes/default/text/resetpw.ini", F_OK) = -1 ENOENT
(No such file or directory)
access("/home/bbs/mystic/themes/scbbs_en/text/resetpw.ini", F_OK) = -1 ENOENT
(No such file or directory)
gettimeofday({tv_sec=1657565833, tv_usec=72114}, NULL) = 0
(cut)
write(28, "2022.07.11 20:57:14 SMTP R:250 HELP\n", 36) = 36
close(28) = 0
open("resetpw.ini", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
(cut)
open("/home/bbs/mystic/logs/node2.log", O_WRONLY|O_APPEND|O_LARGEFILE) = 28
write(28, "2022.07.11 20:57:14 SMTP S:MAIL FROM:\n", 65) = 65
(cut)
I'm not sure what the CWD is for the last open() there, but suspect it might
be the Mystic main directory (/home/bbs/mystic).
After copying resetpw.ini to /home/bbs/mystic/themes/scbbs_en/text, it manages
to find it:
write(1, "\33[0;1;30m\33[0;1;33mSending password reset e-mail... \33[?25l",
57) = 57
access("/home/bbs/mystic/themes/scbbs_en/text/resetpw.ini", F_OK) = 0
...but still fails to open it:
write(28, "2022.07.11 21:05:46 SMTP R:250 HELP\n", 36) = 36
close(28) = 0
open("resetpw.ini", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or
directory)
So perhaps there are two things that would need to be adjusted -- that it
should check the "global" data directory as a fallback (before resorting to
the hard-coded message in MIS), and that it should attempt to open the file it
determined to use using its full path?
g0> BW> menu command: If the command list is already full (25 entries), pasti
g0>
g0> I'll have it pop up a note that says "max items reached" or something
g0> along those lines.
Sounds great! That will do just fine.
g0> Also you can stack actual menu commands too so for example if you
g0> reached the menu action limit for a specific hotkey you can create
g0> another one with a blank text under it with the same hotkey, and Mystic
g0> will execute the action lists for both.
Thanks for the tip! Yes, I have a bunch of those (although not for a certain
hotkey, but rather for FIRSTCMD) in the prelogin menu, and that's actually
where I had to split one of the steps during login (e-mail validation) further
because I exceeded the limit. :)
But no harm done, as that menu already contains many FIRSTCMDs for the
different steps/checks performed during login. :)
g0> BW> * I have Disable Time: No and a security level (s255) which has Time
g0> BW> Day: 9999. Do Shell events with Warning: x (minutes) really kick the
g0> BW> user out? I would expect Mystic to trim the available time (9999
g0>
g0> It probably doesn't when you disable the entire time system I would have
g0> to check into that. I am pressed for time right now so I don't have
g0> time to take a look to refresh my memory.
No problem!
Although "Disable Time: No" means time accounting enabled, right?
I actually re-enabled it a while ago as I thought that disabling it was the
cause of users not getting kicked out. But it appears that it doesn't matter if
it's enabled or not -- users still don't seem to get kicked out at event time.
So that might be something to test whenever you get time. :)
g0> But this entire area could use some work!
Actually it works just fine otherwise!
Again, thanks a lot!
Best regards
Bj”rn
--- Mystic BBS v1.12 A48 2022/07/11 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 120/340 616
SEEN-BY: 123/10 120 131 124/5016 129/215 305 330 331 153/757 7715
SEEN-BY: 154/10 30 40 50 700 201/0 137 203/0 124 218/700 840 220/70
SEEN-BY: 220/90 221/0 1 6 226/17 18 30 100 227/114 201 229/110 111
SEEN-BY: 229/112 113 206 307 310 317 400 424 426 428 452 470 550 664
SEEN-BY: 229/700 230/0 240/5832 250/5 8 266/512 267/800 280/464 5003
SEEN-BY: 282/1038 292/854 8125 298/25 301/1 305/2 3 317/3 320/219
SEEN-BY: 322/757 341/234 342/200 396/45 460/58 633/280 712/848 770/1
SEEN-BY: 2320/105 2452/250 3634/12 24
PATH: 201/137 0 203/0 280/464 154/10 770/1 317/3 229/426
|
