Hello, Wilfred.

03 Mar 15 09:30, you wrote to Michael Dukelsky:

 WV> Hi,

 WV> On 2015-03-03 08:26:44, Michael Dukelsky wrote to Marcin Lukasik:
 WV>   about: "Applying nodediffs with nlupdate":

 ML>>> I've recently set up my Fidonet point, and I've run into many
 ML>>> issues, most of which I've been able to solve - but not this
 ML>>> one: I have recent 'NODELIST' file in /home/fido, all of which
 ML>>> is properly described in husky config; and yet, when I run
 ML>>> nlupdate, it outputs nothing, and in the log it says that 'No
 ML>>> instance of nodelist NODELIST found.'. strace reveals that
 ML>>> nlupdate, as would be expected, looks in the nodelist directory,
 ML>>> but for some reason it doesn't notice the file. I don't know
 ML>>> what else to specify, since I haven't been able to find out
 ML>>> anything more. I'd be grateful for any help.

 MD>> Do you pay for the IP traffic? If not, it is better to use the
 MD>> full nodelist from the DAILYLST fileecho, since the majority
 MD>> nowadays seems to use the full nodelist and therefore there is
 MD>> nobody willing to fix bugs in nlupdate.

 WV> Are there known bugs in nlupdate? I use it both on windows and linux
 WV> to apply the nodediff to the nodelist succesfully every week. So why
 WV> shouldn't it work for Marcin?

 WV> Bye, Wilfred.


 WV> --- FMail-W32-1.69.1.95-B20140716

Okay, we've figured it out - it was a configuration issue stemming from my
misunderstanding of the naming of nodelist files.

Marcin Lukasik

--- GoldED+/LNX 1.1.5-b20130910