Subj : Re: Event Timing
To   : 2twisty
From : McDoob
Date : Thu Mar 31 2022 11:46 pm

 2t>  Mc> Let ./mis (and ./mutil) take care of Mystic. Don't ask the end user's
 2t>  Mc> to do it instead. That's a bad habit that programmers should avoid. I
 2t>  Mc> would pretend to know.
 2t> 
 2t> If Mystic gave me that option, I wouldn't use a workaround.  But if (for
 2t> some reason) I need to run things with control levels that Mystic
 2t> doesn't allow, then you could use cron (or any other tool that you want
 2t> to use to force mystic to execute an event via semaphore)

Well...you're not wrong...you could always add '/dir-of-mystic/mutil whatever.ini' to your crontab...

I still maintain (mantain? maintane? whatever) the belief that this is not the way it *should* be done. It certainly isn't be the OS's responsibility to keep the software up-to-date. In a perfect digital world, every program would exist in its own 'bubble'. 

This is exactly what many OSes have tried (and usually failed) to do!

One of my teachers once said "Every lazy step is a hacker's exploit." I'm inclined to believe him, because I've seen proof.

McDoob
SysOp, PiBBS
pibbs.sytes.net

.... Some people have no idea what they're doing, and are really good at it!

--- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)
 * Origin: PiBBS (21:4/135)

.