Subj : Re: Hatching Files
To   : Netsurge
From : Tony Langdon
Date : Fri Jun 07 2019 09:01 am

-=> On 06-06-19 13:43, Netsurge wrote to All <=-

 Ne> Does anyone know if you can hatch a file out via the command line
 Ne> without using the autohatch feature of mutil.

 Ne> I want to hatch nodelist and nodediff updates for a network
 Ne> automatically but the extension will be different each week. Is there a
 Ne> wildcard option for autohatch? I have tried * and ? to no avail.

 Ne> I could script changing the name in the mutil.ini file but I was hoping
 Ne> there was a simpler way to do this.

My script does all of this outside of Mystic, using Linux BASH scripting.  My
hatching system dates back before Mystic gained file hatching capability
internally, and simulates another system (using a dedicated FTN address)
placing the files into Mystic's inbound.

As for the extension issue, the script writes a file with the current filename
being hatched, when it finishes hatching the file, so next time it runs (and
hatches) the nodelist, the old filename is available for inserting into the
Replaces field or whatever other programming is required.  And of course, BASH
can do the wildcard searches in the directory for the current filename.

I've kept my file hatching system going, because (1) it works, and (2) it fits
in with other parts of my system that run around the same time - nodelist
generation, nodelist to DNS conversion, etc.


.... And now for something you'll really like! -Rocky
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.