Hopefully, someone else has seen this... and hopefully Mystic BBS's are not being hacked... Thanks, for any help!
-------->> start concerning entries <<------------
2022.10.18 13:36:06 Executing: sh /mystic/temp2/xfer.sh
2022.10.18 13:36:06 Execution complete: 32512
-------->> start concerning entries <<------------
2022.10.18 13:36:06 Executing: sh /mystic/temp2/xfer.sh
2022.10.18 13:36:06 Execution complete: 32512
-------->> end concerning entries <<--------------
On 18 Oct 2022 at 07:18p, Clive Reuben pondered and said...
-------->> start concerning entries <<------------
2022.10.18 13:36:06 Executing: sh /mystic/temp2/xfer.sh
2022.10.18 13:36:06 Execution complete: 32512
-------->> end concerning entries <<--------------
Here we go, found it. It's mentioned in whatsnew.txt from back in the development of 1.08
[snip]
+ Added the ability to execute an MPL program instead of the command line
for a protocol. By starting your command line with a !, you can have
Mystic run a MPE program. For example:
send Command: !test %1 %2 %3
The above would execute test.mpe from your scripts directory and pass
the results of the %1 %2 %3 protocol MCI codes as command parameters
to the MPL program. Keep in mind that if you do use this to execute some type of protocol, you must set the DSZLOG environment variable yourself and have it point to the current node's temp directory as xfer.log. Mystic will also create an xfer.bat or xfer.sh (depending
on operating system) which
can also be executed.
Ok... So, it really is just a normal system function then? I could not find it anywhere else in the logs and couldn't recreate it... Thanks,
very much for letting me know!!! Much appreciated!
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 155:13:36 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,379 |