I can see a certain nodelist is being merged with mutil (I have 3 and it
shows 3 nodelists merged). But at my message menu when I (B)rowse Nodelists
and search LIST ZONES it only shows two zones... any reason why the 3rd
doesn't show?

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: ._.-. nightvault.fsxnet.nz port 2323 .-._. (21:3/112)

On 26 Oct 2021, fang-castro said the following...

I can see a certain nodelist is being merged with mutil (I have 3 and it shows 3 nodelists merged). But at my message menu when I (B)rowse Nodelists and search LIST ZONES it only shows two zones... any reason
why the 3rd doesn't show?

I've noticed in the past that Mystic will only process .### (e.g .123) or
.Z## (e.g. .Z23) files and will ignore .ZIP files completely. I had to unzip micronet.zip before Mystic will compile that nodelist.

If I could get you could set loglevel = 3 in that .ini file and run it again and then post that section of your mutil.log. That should give us some hints as to what the issue is.


Jay

... Remind me never to put off until tomorrow the things I've already put off

--- Mystic BBS v1.12 A47 2021/10/25 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

On 26 Oct 2021, Warpslide said the following...

I can see a certain nodelist is being merged with mutil (I have 3 and shows 3 nodelists merged). But at my message menu when I (B)rowse Nodelists and search LIST ZONES it only shows two zones... any reason why the 3rd doesn't show?

I've noticed in the past that Mystic will only process .### (e.g .123) or .Z## (e.g. .Z23) files and will ignore .ZIP files completely. I had to unzip micronet.zip before Mystic will compile that nodelist.

If I could get you could set loglevel = 3 in that .ini file and run it again and then post that section of your mutil.log. That should give us some hints as to what the issue is.

Definitely some weirdness... the nodelist filename is HOBBYNET.302
Logfile:

+ Oct 26 12:02:52 Searching "/home/xxx/mystic/temputil/* for nodelist
"TQWNET" + Oct 26 12:02:52 Found "tqwnet.232"
+ Oct 26 12:02:52 Compare tqwnet.232 2021 / 1980
+ Oct 26 12:02:52 Result 1
+ Oct 26 12:02:52 Merging /home/xxx/mystic/temputil/tqwnet.232
+ Oct 26 12:02:52 Merging HOBBYNET
+ Oct 26 12:02:52 Searching "/home/xxx/mystic/* for archive "HOBBYNET "
+ Oct 26 12:02:52 Searching "/home/xxx/mystic/* for nodelist "HOBBYNET "
+ Oct 26 12:02:52 Searching "/home/xxx/mystic/temputil/* for nodelist "HOBBYNET " + Oct 26 12:02:52 Results: Merged 3 of 3 nodelist(s) in 0.03s

lmfao... there was a bunch of spaces in the .ini file after the nodelist
name. all fixed! thanks!

|08__ _ _ ____ |02_ _ |10___ _ _ |02____ |08_ _ _ ___
|08| \| | |__\ |02|--| |10 | \/ |02|--| |08|__| |___ |

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: ._.-. nightvault.fsxnet.nz port 2323 .-._. (21:3/112)

I've noticed in the past that Mystic will only process .### (e.g .123) or .Z## (e.g. .Z23) files and will ignore .ZIP files completely. I had to unzip micronet.zip before Mystic will compile that nodelist.

Man, you know...

I'm glad I'm not the only one having this problem with Micronet nodelists. It's not the only one giving me troubles either. I thought it was something I was doing wrong.

I wonder what the best way to deal with that is. The micronet.zip file contains two files:

micronet.123
file_id.diz

[*] Is there an FTN standard for nodelist file naming/packing format? Is this off-standard, or does Mystic just lack the functionality to deal with a nodelist packaged in this way?

[*] I am wondering what the best way to handle this situation in an automated fashion is. Now that your report suggests it is not, as I always assume to be the case, grotesque incompetence on my part, I am experimenting with the following job to run Saturdays (the nodelists are delivered for Micronet on Friday):

#!/bin/bash

cd /mystic/files/micronet/MIN_LIST
if [[ -f /mystic/files/micronet/MIN_LIST/micronet.zip ]]; then
unzip /mystic/files/micronet/MIN_LIST/micronet.zip
rm /mystic/files/micronet/MIN_LIST/file_id.diz
cd /mystic
./mutil ./maint.ini
fi

This seems to work. However, it leaves the .123 file in the directory where it gets snarfed up by the file base, separate from the .zip file. I can live with that for now. I would have to break my maint.ini into two parts, moving the [MassUpload] to a new file. So then:

[1] Run the above, unzip.
[2] Run maint.ini without the mass upload
[3] Delete the .123 file
[4] Run the new maint2.ini with the mass upload option so it doesn't upload the .123 file to the Micronet Nodelist file base.

I include all of this detail here in hopes someone can suggest a simpler way of handling this, not that this is overcomplicated or anything, but it requires adding complexity, which I hate.

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

On 26 Oct 2021, DustCouncil said the following...

I wonder what the best way to deal with that is.

Here's what I do:

[--- begin nodelist.sh ---]
rm -f /home/pi/mystic/micronet.*
unzip /home/pi/mystic/files/fdn_MIN_LIST/MICRONET.ZIP micronet.* -d /home/pi/mystic
cd /home/pi/mystic
./mutil nodelist.ini -NOSCREEN
[--- end nodelist.sh ---]

(/home/pi/mystic should be on the same line as the unzip command)

This will unzip anything in MICRONET.ZIP named micronet.* to the /home/pi/mystic directory.

I then just tell my nodelist.ini to look for the file in my mystic directory:

nodefile=/home/pi/mystic/files/fdn_FSX_NODE/FSXNET nodefile=/home/pi/mystic/files/fdn_NODELIST/NODELIST nodefile=/home/pi/mystic/files/fdn_SCINODE/scinet nodefile=/home/pi/mystic/micronet nodefile=/home/pi/mystic/files/fdn_METRONET/METLIST nodefile=/home/pi/mystic/files/fdn_rtn_nodelist/retronet nodefile=/home/pi/mystic/HOBBYNET

Hobbynet nodelists get sent manually via email, so I just dump the latest one in the same directory, replacing as necessary.


Jay

... The quickest way to make your own anti-freeze is to hide her nightie.

--- Mystic BBS v1.12 A47 2021/10/25 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Here's what I do:

That's cleaner. I will probably take that approach. Thanks!

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)