• Re: Duplicate nodelist/in

    From Mike Powell@954:895/54 to DAN CLOUGH on Saturday, February 21, 2026 10:47:54
    @MSGID: <69987B66.584.hnet_hnetsyso@capcity2.synchro.net>
    @REPLY: <69967593.582.hnet_hnetsyso@capcity2.synchro.net>
    Re: Re: Duplicate nodelist/infopack received
    By: Mike Dippel to Mickey on Wed Feb 18 2026 08:07 pm

    Just wanted to let you know that I've received the latest HOBBYNET.ZIP and HOBBYNET.044 twice for unknown reasons.

    Once last night (Feb 12th) at 11:15 PM, CST
    Again this morning (Feb 13th) at 4:01 AM, CST

    HEY!!!! I only got ONE copy. :-)

    Dan is special!

    This same thing happened again last night, at nearly the identical times. I'm
    sure I can't be the only one getting things twice...

    Is it possible that maybe you have two net/node numbers set up on your hub
    and don't know it?

    I only *seem* to be getting it once... one of each. That said, I do not
    seem to have an entry for it in my tickit.ini file so I have no idea how
    tickit seems to know where to put them, or to "replace" them if I accidentally get two!

    Mike P.


    * SLMR 2.1a * Exxon - greasing the coastline for smoother boating!
    --- SBBSecho 3.28-Linux
    * Origin: Capitol City Online (954:895/54)
  • From Dan Clough@954:200/1 to Mike Powell on Saturday, February 21, 2026 21:24:36
    Mike Powell wrote to DAN CLOUGH <=-

    Re: Re: Duplicate nodelist/infopack received
    By: Mike Dippel to Mickey on Wed Feb 18 2026 08:07 pm

    Just wanted to let you know that I've received the latest HOBBYNET.ZIP and HOBBYNET.044 twice for unknown reasons.

    Once last night (Feb 12th) at 11:15 PM, CST
    Again this morning (Feb 13th) at 4:01 AM, CST

    HEY!!!! I only got ONE copy. :-)

    Dan is special!

    This same thing happened again last night, at nearly the identical times.
    I'm
    sure I can't be the only one getting things twice...

    Is it possible that maybe you have two net/node numbers set up on your
    hub and don't know it?

    Hmmmm, I suppose that is possible, and is actually a question for Mike Dippel...

    Mike, remember I used to just have a node number - 954:895/xxx (can't
    recall those last digits now). Then when I became a hub... did that
    first entry get removed? So now I am 954:200/0 and 954:200/1 ...

    Could you check that you're not sending to the (old/incorrect) address,
    and only to the 954:200/1 address? Thank you.

    And thanks, Mike, for that insight. ;-)

    I only *seem* to be getting it once... one of each. That said, I do
    not seem to have an entry for it in my tickit.ini file so I have no
    idea how tickit seems to know where to put them, or to "replace" them
    if I accidentally get two!

    Now that's unusual, indeed! Wouldn't seem like tickit would do anything
    with them.



    ... Gone crazy, be back later, please leave message.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.34-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (954:200/1)
  • From Mike Powell@954:895/54 to DAN CLOUGH on Sunday, February 22, 2026 10:24:39
    Could you check that you're not sending to the (old/incorrect) address,
    and only to the 954:200/1 address? Thank you.

    And thanks, Mike, for that insight. ;-)

    That is just a wild guess on my part. Be interesting if that is the issue
    as it'd be easy to fix.

    I only *seem* to be getting it once... one of each. That said, I do
    not seem to have an entry for it in my tickit.ini file so I have no
    idea how tickit seems to know where to put them, or to "replace" them
    if I accidentally get two!

    Now that's unusual, indeed! Wouldn't seem like tickit would do anything
    with them.

    I will have to look it over when I get more time. It must be in there somewhere and I am just overlooking it. But it is working as I think it
    should so I don't want to break it. ;)

    Mike P

    * SLMR 2.1a * A paid up computer is, by definition, obsolete.
    --- SBBSecho 3.28-Linux
    * Origin: Capitol City Online (954:895/54)
  • From Dan Clough@954:200/1 to Mike Powell on Sunday, February 22, 2026 15:12:29
    Mike Powell wrote to DAN CLOUGH <=-

    Could you check that you're not sending to the (old/incorrect) address,
    and only to the 954:200/1 address? Thank you.

    And thanks, Mike, for that insight. ;-)

    That is just a wild guess on my part. Be interesting if that is the
    issue as it'd be easy to fix.

    Yep, it would be.

    I only *seem* to be getting it once... one of each. That said, I do not seem to have an entry for it in my tickit.ini file so I have no idea how tickit seems to know where to put them, or to "replace" them if I accidentally get two!

    Now that's unusual, indeed! Wouldn't seem like tickit would do anything with them.

    I will have to look it over when I get more time. It must be in there somewhere and I am just overlooking it. But it is working as I think
    it should so I don't want to break it. ;)

    Hahaha, I hear that!

    This should tell something: grep HNET /sbbs/ctrl/tickit.ini




    ... Gone crazy, be back later, please leave message.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.34-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (954:200/1)
  • From Robert Wolfe@954:895/1 to Dan Clough on Thursday, February 26, 2026 10:13:00
    .On Feb 25, 2026 10:59am, DAN CLOUGH wrote to MIKE DIPPEL:

    Mike Dippel wrote to Dan Clough <=-

    Well, I am receiving them twice, about 5 hours apart, from your
    system.
    That right there is the problem. Should be easy enough to confirm
    in
    your logs that the files were sent out twice. The question is *WHY*
    are
    they being sent out twice?

    As Mike asked, is anyone else seeing this? Please speak up if you
    are.

    Mike, as I said in another message last night (as a reply to
    somebody
    else), is it possible that I am in your nodelist/database twice? I
    used
    to have a different node number...

    Sorry. I can't see it on my log files. Can you tell me the date
    and
    times and I can check again.

    February 12th at 12:15 AM (EST)
    February 13th at 5:01 AM (EST)

    I only keep log files for 7 days so I can't check it. If it happens
    again, I can check it if you provide me the info.

    Well, the above reference was for Feb 12/13. It happened again the following week (Feb 19/20) which is what was stated right here in this message thread. So.... the 19/20 events should still be visible in the logs, right?

    How can I be the only one noticing this?

    þ wcQWK 10.0 ÷ HobbyNet: Hobby Line BBS | hobbylinebbs.com

    I don't see it because I am getting the network via QWK.
    ---
    þ wcQWK 10.0 ÷ HobbyNet: Over The Brink BBS ¦ brinkbbs.org
    * Origin: The Hobby Line! BBS - hobbylinebbs.com (954:895/1)
  • From Robert Wolfe@954:895/1 to Dan Clough on Thursday, February 26, 2026 10:14:00
    .On Feb 25, 2026 03:10pm, DAN CLOUGH wrote to THE WANDERER:

    Thank you! I was starting to think I was the only Sysop who looks at logs... ;-)

    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (954:200/1)
    þ wcQWK 10.0 ÷ HobbyNet: Hobby Line BBS | hobbylinebbs.com

    I get a headache looking at mine sometimes. :)
    ---
    þ wcQWK 10.0 ÷ HobbyNet: Over The Brink BBS ¦ brinkbbs.org
    * Origin: The Hobby Line! BBS - hobbylinebbs.com (954:895/1)