Hello Nicholas!

11 Jun 20 14:45, you wrote to g00r00:

 jS>>> + Jun 10 20:13:39  Results: Auto-create prefix path does not
 JS>>> exist:  in

 gr>> So it looks like its saying dir_prefix is set to a invalid/blank
 gr>> value.

 NB> It seems as though he's trying to actually prefix his directory name,
 NB> ie: fido_, So Mystic seems to be telling him that
 NB> ../mystic/files/fido_ doesn't exist. I've always understood the
 NB> "Prefix Directory" as just that (the path to the actual directory),
 NB> and not an actual prefixed directory name. Unless you've already added
 NB> this functionality in, it may be something entirely new.

I had thought of that too. As a test I created the prefix path fido_ under
/home/mystic/files. I got the same response when running Mutil. It didn't
seem to matter if /home/mystic/files or /home/mystic/files/fido_ existed.
The docs led me to think that Mystic would create the prefix path specified
when a file/tic was precessed for an unknown fileecho. As in /fido_nodelist
when a file for say the nodelist file echo was received. Please correct any
misunderstanding that I might have.

Jeff


--- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303