Hi Rick,

On 2022-12-20 06:42:04, you wrote to me:

 RS>>> Im curious how everyone is updating nodelist on receipt of either
 RS>>> a diff or weekly update, seems I have to do it manually?

 WV>> No. But it's a bit of a "chain" to setup.

 WV>> Whenever there are .tic files received by my mailer htick is run like
 WV>> this:

 WV>>   .../htick -c .../husky.config toss

 WV>> In my husky.config I have the following lines:

 WV>>   FileArea NODEDIFZ [FileAreaDir]/nodedifz -g FidoNet -d "Nodediffs in
 WV>> zip format" -a 2:280/464 2:.../... [...] # === Fidonet Worldwide
 WV>> Nodelist === Nodelist        NODELIST DiffUpdate
 WV>> [FileAreaDir]/nodedifz/NODEDIFF NodelistFormat  Standard DefaultZone
 WV>> 2 [...] ExecOnFile  NODEDIFZ  NODEDIFF.Z??  [basedir]/bin/nlupdate.sh


 WV>> ('...' are paths on my system)


 RS> I think I see how this works, one question just after your FileArea line
 RS> and before the #=== line you have [...] which you said indicates a path on
 RS> your system, is this a change in path or directory here? and if so where do
 RS> I need to be pointing?  Thank you!

Ok, sorry for the confusion. In the husky.config section '[...]' it has the regular meaning of left out lines. ;-)
And in reality I don't have 1 big husky.config file, but it is split up in a few sections that are included in the main file.

The only explicit change in path (with a cd command) I do, is before gnlnx that needs to be executed in the directory where the golded config files reside.


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815