Subj : Re: Finally working.. here's what was wrong
To   : Fratm
From : Zip
Date : Fri Aug 06 2021 21:09:26

Hello Fratm!

On 06 Aug 2021, Fratm said the following...
 Fr> So I was having result code 127 ever time my even't would run.  After a
 Fr> long bit of trouble shooting I figured out that it was not finding my
 Fr> mutil app.  In events I was not specifing the path to mutil.  That

When Mystic launches events, it places itself in the Mystic base directory (e.g. "/mystic"), i.e., that will be the current working directory for the commands that you specify on the command line.

Unless you have the Mystic base directory in your BBS user's PATH, you will need to either use the full path to mutil (e.g. "/mystic/mutil") or, as the mutil binary should be in the Mystic base directory, simply prepend them with "./" (= current directory), e.g. "./mutil".

Best regards
Zip

--- Mystic BBS v1.12 A47 2021/08/05 (Linux/64)
 * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

.