• Nodelist Browser Problem

    From KB2MOB@21:1/176 to All on Monday, November 07, 2016 10:09:00
    Hey folks!

    Having an issu where only 1 nodelist seems to be showing results. Not sure
    what is going on. I have checked the mutil log for maint and it shows it doesn't see the nodelist for retronet, or fido. I went through the
    settings and everything looks ok with dir paths.

    Could it be a matter of case? I'm on Linux and the FSX nodelist filename is
    all caps, while the other are lowercase. But the case matches in the ini file as well. Just not sure why it's not going...

    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Radio Freqs & Geeks BBS (21:1/176)
  • From Night Stalker@21:1/178 to KB2MOB on Saturday, November 12, 2016 00:45:00

    Having an issu where only 1 nodelist seems to be showing results. Not
    sure what is going on. I have checked the mutil log for maint and it
    shows it doesn't see the nodelist for retronet, or fido. I went through the settings and everything looks ok with dir paths.

    Could it be a matter of case? I'm on Linux and the FSX nodelist filename is all caps, while the other are lowercase. But the case matches in the ini file as well. Just not sure why it's not going...


    Try renaming the nodelist so it's all lower case.. this is especially
    important for linux because FSXNET.XXX and fsxnet.xxx can both exist in the same folder

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)
  • From bcw142@21:1/122 to KB2MOB on Saturday, November 12, 2016 10:41:00
    On 11/07/16, KB2MOB said the following...
    Could it be a matter of case? I'm on Linux and the FSX nodelist filename is all caps, while the other are lowercase. But the case matches in the ini file as well. Just not sure why it's not going...
    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Radio Freqs & Geeks BBS (21:1/176)

    Yes, case matters on Linux. You can do multiple enteries:
    nodefile=/mystic/files/fsx_node/fsxnet
    nodefile=/mystic/files/fsx_node/FSXNET
    nodefile=/mystic/files/rtn_nodelist/RETRONET
    nodefile=/mystic/files/rtn_nodelist/retronet

    Also if that doesn't seem to work try unpacking the list to the file area.
    Is data/nodelist.txt being made? If you look at it with an editor are there multiple ^Z (control-Z) in the body of the file (likely one at end)?

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Necronomicon BBS - necrobbs.strangled.net (21:1/122)
  • From Avon@21:1/101 to KB2MOB on Sunday, November 13, 2016 08:11:00

    On 11/07/16, KB2MOB pondered and said...

    Having an issu where only 1 nodelist seems to be showing results. Not
    sure what is going on. I have checked the mutil log for maint and it
    shows it doesn't see the nodelist for retronet, or fido. I went through the settings and everything looks ok with dir paths.

    Could it be a matter of case? I'm on Linux and the FSX nodelist filename is all caps, while the other are lowercase. But the case matches in the ini file as well. Just not sure why it's not going...

    Hi there... as others have already replied I'll just add my 2 cents... I
    agree it's like to be a case issue in the way your nodefile line is
    specified. Just also check the path is correct and it's a path for linux and not windows.. also check you have unzip installed... but I'd say it's very likely you do. Set you mutil log to level 3 and feel free to post it's
    relevant output here if you are still having probs :)

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@1:1/0 to KB2MOB on Saturday, November 12, 2016 10:01:00
    On 11/07/16, KB2MOB said the following...
    Having an issu where only 1 nodelist seems to be showing results. Not
    sure what is going on. I have checked the mutil log for maint and it
    shows it doesn't see the nodelist for retronet, or fido. I went through the settings and everything looks ok with dir paths.
    Could it be a matter of case? I'm on Linux and the FSX nodelist filename is all caps, while the other are lowercase. But the case matches in the ini file as well. Just not sure why it's not going...
    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Radio Freqs & Geeks BBS (21:1/176)

    Yes, case matters but you can have multiple entries to handle that:
    nodefile=/mystic/files/fsx_node/FSXNET
    nodefile=/mystic/files/fsx_node/fsxnet

    I've also found nodelists that end in ^Z (Control-Z) and it seems to stop reading there, I edited the data/nodelist.txt to get rid of the ^Z and that helped. The data/nodelsit.txt has no problem with a ^Z at the end of the
    file, but doesn't seem to handle them inside the body of the file. I still
    have problems as there seems to be a limit on the length of the node list it will respond to, but I'm not sure if the limit is on the nodelist itself or
    the node2bbi or blam2 which I'm looking at it with.

    Another trick if the two entries (upper and lower case) doesn't work is to unpack the nodelist and leave it in the directory with right filename and
    case.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org
  • From KB2MOB@21:1/176 to Avon on Tuesday, November 15, 2016 00:22:00
    Hey all! I finally got it figured out.

    First was a typo. Not sure how I missed it. But there it was once I took another hard look at the ini file.

    The other was, one of the nodelists, the name of the file was lowercase, but the compressed file name was UPPER. So when Mystic uncompressed the file, it was looking for an UPPERCASE file, and there was none. So I renamed the file, recompressed it, and tried it, and it worked.

    Thanks for all the help guys and gals! I appreciate it!
    -MobbyG, KB2MOB

    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Radio Freqs & Geeks BBS - Albany, NY (FN32DO) (21:1/176)
  • From Night Stalker@21:1/178 to bcw142 on Saturday, November 19, 2016 21:21:00
    Yes, case matters but you can have multiple entries to handle that:
    nodefile=/mystic/files/fsx_node/FSXNET
    nodefile=/mystic/files/fsx_node/fsxnet

    I've also found nodelists that end in ^Z (Control-Z) and it seems to stop reading there, I edited the data/nodelist.txt to get rid of the ^Z and that helped. The data/nodelsit.txt has no problem with a ^Z at the end
    of the file, but doesn't seem to handle them inside the body of the
    file. I still have problems as there seems to be a limit on the length
    of the node list it will respond to, but I'm not sure if the limit is on the nodelist itself or the node2bbi or blam2 which I'm looking at it
    with.


    Easy solution for linux folks having problems with nodelists.. because most nodelists are created using DOS/Windows tools CR/LF aren't translated to Unix properly... Install dos2unix or tofrodos

    dos2unix <nodelist> (for dos2unix)
    frodos <nodelist> (for tofrodos)

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: internal dimension ÷ idbbs.dlinkddns.com ÷ port 59 (21:1/178)