1. Forum
  2. tqwNet
  3. TQW SUG

  • Docker Chat

    From poindexter FORTRAN@1337:3/178 to All on Thu Jul 25 17:30:43 2024

    Could we rename the "Docker Chat" echo to "Container Chat"? I know a lot of sysops and home labbers are using Proxmox, which supports LXC containers natively. I bet we could get some more traffic in there if we got people talking about LXC.
    --- SBBSecho 3.20-Win32
    * Origin: realitycheckBBS.org -- information is power. (1337:3/178)
  • From Ernest J Gainey Iii@1337:3/108 to poindexter FORTRAN on Thu Jul 25 23:35:43 2024
    Re: Docker Chat
    By: poindexter FORTRAN to All on Thu Jul 25 2024 05:30 pm

    I use both, so I wouldn't be against it.

    Could we rename the "Docker Chat" echo to "Container Chat"? I know a lot of sysops and home labbers are using Proxmox, which supports LXC containers natively. I bet we could get some more traffic in there if we got people talking about LXC.

    ===
    Ernest J Gainey III
    Lost Cause Halfway House
    bbs.lostcause.house
    --- SBBSecho 3.20-Linux
    * Origin: Lost Cause Halfway House - bbs.lostcause.house (1337:3/108)
  • From Warpslide@1337:3/100 to poindexter FORTRAN on Fri Jul 26 07:18:52 2024
    On 25 Jul 2024, poindexter FORTRAN said the following...

    @AREA:TQW_SUG
    @TZUTC: -0700
    @MSGID: 1.tqw_sug@1337:3/178 2b0823df
    @PID: Synchronet 3.20a-Win32 master/37dc6b28e Jul 09 202 MSC 1916
    @TID: SBBSecho 3.20-Win32 master/37dc6b28e Jul 09 2024 20:40 MSC 1916 @BBSID: REALITY
    @CHRS: ASCII 1
    @NOTE: SlyEdit 1.89b (2024-05-11) (ICE style)
    @TZUTC: -0700
    @MSGID: 2.tqw_sug@1337:3/178 2b082435
    @PID: Synchronet 3.20a-Win32 master/37dc6b28e Jul 09 202 MSC 1916
    @TID: SBBSecho 3.20-Win32 master/37dc6b28e Jul 09 2024 20:40 MSC 1916 @BBSID: REALITY
    @CHRS: ASCII 1
    @NOTE: SlyEdit 1.89b (2024-05-11) (ICE style)
    @PATH: 3/178 178 100

    Could we rename the "Docker Chat" echo to "Container Chat"? I know a lot of sysops and home labbers are using Proxmox, which supports LXC containers natively. I bet we could get some more traffic in there if we got people talking about LXC.
    --- SBBSecho 3.20-Win32
    * Origin: realitycheckBBS.org -- information is power. (1337:3/178)

    This message ended up in my DUPE base here, presumably due to the duplicated headers. I'm assuming the message looks fine on your end?

    I only see this behaviour with tqwNet, I'm wondering if maybe tqw's hub 3 has some message corruption?


    Jay

    ... It is better to know some of the questions than all of the answers

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms
  • From poindexter FORTRAN@1337:3/178 to Warpslide on Fri Jul 26 07:08:00 2024
    Warpslide wrote to poindexter FORTRAN <=-

    This message ended up in my DUPE base here, presumably due to the duplicated headers. I'm assuming the message looks fine on your end?

    I only see this behaviour with tqwNet, I'm wondering if maybe tqw's hub
    3 has some message corruption?

    That's odd, my first thought was that it was a duplicate QWK reply
    packet upload, but I have dupe detection turned on my side and it
    usually catches those.

    This message was entered directly on my system using the FSE.

    Looking at my echo log, I see this:

    2024-07-25 17:33:34 Exporting tqw_sug message #1 from poindexter FORTRAN to All in area: TQW_SUG
    2024-07-25 17:33:34 Creating outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt
    2024-07-25 17:33:34 New packet (type 2+) created for linked-node: 1337:3/100 2024-07-25 17:33:34 Adding TQW_SUG message from poindexter FORTRAN (1337:3/178) to packet for 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt
    2024-07-25 17:33:34 Added TQW_SUG message from poindexter FORTRAN (1337:3/178) to packets for 1 links (exceptions: none)
    2024-07-25 17:33:34 Exporting tqw_sug message #2 from poindexter FORTRAN to All in area: TQW_SUG
    2024-07-25 17:33:34 Appending outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt
    2024-07-25 17:33:34 Adding TQW_SUG message from poindexter FORTRAN (1337:3/178) to packet for 1337:3/100: c:\sbbs\temp\sbbsecho\66a2eede.pkt
    2024-07-25 17:33:34 Added TQW_SUG message from poindexter FORTRAN (1337:3/178) to packets for 1 links (exceptions: none)
    2024-07-25 17:33:34 Exported: 2 msgs tqw_sug -> TQW_SUG
    2024-07-25 17:33:34 Exported: 2 msgs total
    2024-07-25 17:33:34 Finalizing outbound packet from 1337:3/178 to 1337:3/100: c:\sbbs\

    It looks like I may have sent out duplicates with duplicate headers?
    I'll forward this to Rob.



    --- MultiMail/Win v0.52
    * Origin: realitycheckBBS.org -- information is power. (1337:3/178)