Subj : Re: Docker Chat
To   : poindexter FORTRAN
From : Warpslide
Date : Fri Jul 26 2024 07:18:52

On 25 Jul 2024, poindexter FORTRAN said the following...

 pF> @AREA:TQW_SUG
 pF> @TZUTC: -0700
 pF> @MSGID: 1.tqw_sug@1337:3/178 2b0823df
 pF> @PID: Synchronet 3.20a-Win32 master/37dc6b28e Jul 09 202 MSC 1916
 pF> @TID: SBBSecho 3.20-Win32 master/37dc6b28e Jul 09 2024 20:40 MSC 1916
 pF> @BBSID: REALITY
 pF> @CHRS: ASCII 1
 pF> @NOTE: SlyEdit 1.89b (2024-05-11) (ICE style)
 pF> @TZUTC: -0700
 pF> @MSGID: 2.tqw_sug@1337:3/178 2b082435
 pF> @PID: Synchronet 3.20a-Win32 master/37dc6b28e Jul 09 202 MSC 1916
 pF> @TID: SBBSecho 3.20-Win32 master/37dc6b28e Jul 09 2024 20:40 MSC 1916
 pF> @BBSID: REALITY
 pF> @CHRS: ASCII 1
 pF> @NOTE: SlyEdit 1.89b (2024-05-11) (ICE style)
 pF> @PATH: 3/178 178 100
 pF> 
 pF> Could we rename the "Docker Chat" echo to "Container Chat"? I know a lot
 pF> of sysops and home labbers are using Proxmox, which supports LXC
 pF> containers natively. I bet we could get some more traffic in there if we
 pF> got people talking about LXC.
 pF> --- SBBSecho 3.20-Win32
 pF>  * 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

.