It took me entirely too long to figure out why my events were failing! And it all came down to exactly two characters in the command line: "./"
In linux, for some obscure reason, most executables (definitely mutil and fidopoll) need to be preceded by the current dir, or "./" (ie ./mutil and ./fidopoll).
This is quite a common issue with those using Mystic.
It's not obscure :)
If you want to fix mystic so that you dont need "./" then you have a couple of options (which I havent tested myself, since I dont use it).
* update your PATH to include where mystic is installed, and
That took too long for me to figure out, too. Q_Q
But, eventually, I did!
McDoob
It takes a little time ma man, but you'll figure it out. Some day, I will figure it all out as well. Naw...... probably not. :-)
It took me entirely too long to figure out why my events were failing!
And it all came down to exactly two characters in the command line: "./"
That took too long for me to figure out, too. Q_Q
In linux, for some obscure reason, most executables (definitely mutil a fidopoll) need to be preceded by the current dir, or "./" (ie ./mutil a ./fidopoll).
It's not obscure :)
Linux (and unix in general), looks for executables in your PATH by default, unless you specifically set your path to look for executables
in your current directly (or a specific directory).
The "default path" is normally /bin, /usr/bin and if your root, /sbin, /usr/sbin. Of course it depends on your distro as well as to what they
set the default PATH to.
* softlink mutil fidopoll to /bin or /usr/bin
* update your PATH to include where mystic is installed, and
* write a script that lives in /bin or /usr/bin with the name fidopoll, mutil, etc - and that script does some magic (if it needs to), before launching the those binaries in the appropriate direction
It took me entirely too long to figure out why my events were failing!
And it all came down to exactly two characters in the command line: "./"
Recently, I've gotten into the (bad) habit of accessing Mystic config
from the SysOp menu. I tried several times to update my events after
figuring out the above difference. And there began my second "D'oh!" moment...because McDoob is not a user in the linux OS. Therefore, McDoob 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.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 96 |
Nodes: | 16 (1 / 15) |
Uptime: | 09:53:25 |
Calls: | 4,663 |
Calls today: | 4 |
Files: | 8,491 |
Messages: | 349,777 |