everything is working fine and Mystic is finding the nodelist.
Not sure if anyone has come across this before but I thought I would
share in case it helps anyone.
everything is working fine and Mystic is finding the nodelist.Good man, yep Linux system need to know the case of the nodelist file is correct and I too have been caught before by \NODELIST vs. \nodelist :)
Not sure if anyone has come across this before but I thought I would share in case it helps anyone.
My Fidonet HUB hatches me nodelist files all in capitals eg. NODELIST.Z53 however when this file is unzipped the file inside is nodelist.253.
/mystic/files/NODELIST/NODELIST for example which looks for the node list this case) the line to nodefile=/mystic/files/NODELIST/nodelist
To.......... rEApZ
On 09/09/16, rEApZ said the following...
My Fidonet HUB hatches me nodelist files all in capitals eg.NODELIST.Z53 rE> however when this file is unzipped the file inside is nodelist.253.
Yes case has always been a problem with Linux. The best trick I found is
to have multiple nodelist entries, an upper case and a lower case for each entry. Not sure what the limit is, but likely there is one.
/mystic/files/NODELIST/NODELIST for example which looks for the nodelist rE> this case) the line to nodefile=/mystic/files/NODELIST/nodelist
So I'd put in both to make sure it works.
nodefile=/mystic/files/NODELIST/NODELIST nodefile=/mystic/files/NODELIST/nodelist
It works ;)
nodefile=/mystic/files/NODELIST/NODELIST nodefile=/mystic/files/NODELIST/nodelist
It works ;)
Thanks for that tip!!! That just got my nodelist merge working over
here, too. One thing to note - this doesn't just effect the Linux
version, but also Windows.
- Mark
here, too. One thing to note - this doesn't just effect the Linux
version, but also Windows.
Good to hear it helped, guess we need Avon or someone to add it to the Wiki.
nodefile=/mystic/files/NODELIST/NODELIST nodefile=/mystic/files/NODELIST/nodelist
It works ;)
Thanks for that tip!!! That just got my nodelist merge working over
here, too. One thing to note - this doesn't just effect the Linux
version, but also Windows.
+ Sep 19 00:54:53 Merging fsxnet
+ Sep 19 00:54:53 Extracting FSXNET.Z60
! Sep 19 00:54:53 unzip -oqqjC c:\bbs\files\fsx\fsx_node\FSXNET.Z60 * -d c:\bbs\mystic\temputil\
I have not had this issue with my windows setup, there's just one line and from memory it's lowercase although the filename comes in as uppercase at present. Hmm..
In my case, the directory was upper case and the nodelist was lower
case. After you sent me the email, I tried changing my directory to all lower case and it didn't fix it.
At least we have a solution. I just add the two lines for each nodelist to cover all bases and it works perfectly!
Just trying to debug this a bit further..a few questions..
In your original nodefile line did you have the nodelist file stated at the end of the line?
e.g. nodefile=c:\path\to\files\fsxnet
When it was not working, what do your mutil logs (level 3) show?
What unzip program are you using - pkunzip or infozip or ?
Case should not be an issue in Windows so I'm curious to understand more about what's really going on to cause your problem. :)
Yes, I had d:\WWIVFTN\wwivftn as the line. I tried that in various
I don't need an uppercase variant of my nodefile line to make this work. If this was needed it would have been something I would have needed to do several years ago.
Best, Paul
--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
I need it on my Pi, but it could be something with the version orYep, my Pi seems happy with a single line using a lowercase nodefile
options of unzip. It would depend on what your using like pkunzip or info-zip or whatever and the OS as well.
If you wouldn't mind posting your actual nodelist lines and mutil logging (level 3) that displays what was happening when not working - that would be great.
On 09/20/16, Avon said the following...
Just trying to debug this a bit further..a few questions..
In your original nodefile line did you have the nodelist file stated the end of the line?
e.g. nodefile=c:\path\to\files\fsxnet
When it was not working, what do your mutil logs (level 3) show?
What unzip program are you using - pkunzip or infozip or ?
Case should not be an issue in Windows so I'm curious to understand m about what's really going on to cause your problem. :)
Yes, I had d:\WWIVFTN\wwivftn as the line. I tried that in various
cases, but what I listed is reflected on the line. I also tried it for d:\FSXNET\fsxnet and until I listed each of those lines twice (one upper and the other lower) it didn't work.
I changed the MUTIL log to debugging and it just showed no nodelist matches. No additional information on the issue. I can post the log entries, but it sheds no detail - just no matches.
These are already extracted nodelists and not compressed, but I did install INFOZIP and gave that a try, but no difference.
On 09/19/16, bcw142 pondered and said...
I need it on my Pi, but it could be something with the version or options of unzip. It would depend on what your using like pkunzip or info-zip or whatever and the OS as well.Yep, my Pi seems happy with a single line using a lowercase nodefile statement and path to file name... but the nodelist filename needed to be uppercase in the case of FSXNET as that's how the nodelists are being sent out at the moment... that had done the trick for me.
If you have multiple entries, where some of them are likely not going to work, I would expect that you would get a 'no matches' error.
Are you certain it isn't working? Have you checked the data/nodelist.txt file to be sure it hasn't been updated?
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 163:45:34 |
Calls: | 2,076 |
Calls today: | 2 |
Files: | 11,137 |
Messages: | 947,148 |