1. Forum
  2. USENET
  3. alt.bbs.synchronet

  • SBBS on linux 32-bit

    From Michael2@michael2@FLUXCAP.remove-wwr-this to All on Thu Oct 22 09:17:54 2020
    From Newsgroup: alt.bbs.synchronet

    ok hope I can explain things so that it makes sense

    have 2 32-bit machines vastly different from each other
    machine #1 (fuji)
    Pentium 150mhz 96megs of ram, pcmcia 10/100 network card
    OS Debian Jessie (does not support the cmov instruction set)

    machine #2 (durwood)
    Amd Duron processor 1600mhz 2gigs ram, internal 10/100 network card
    OS Ubuntu 18.04 LTS (32-bit)

    both machines setup as a fidonet point, get the exact same error when polling for mail "Error in recv() of first byte of packet header"

    I have tried increasing the RCVBUF line to 8192 in sockopts.ini thinking just not enough of a buffer but no change.. any ideas?

    Michael

    ---
    þ Synchronet þ fluxcap.synchro.net:5023 - Portland, OR
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Digital Man@digital.man@vert.synchro.net.remove-7gj-this to Michael2 on Thu Oct 22 11:20:39 2020
    From Newsgroup: alt.bbs.synchronet

    To: Michael2
    Re: SBBS on linux 32-bit
    By: Michael2 to All on Thu Oct 22 2020 09:17 am

    ok hope I can explain things so that it makes sense

    have 2 32-bit machines vastly different from each other
    machine #1 (fuji)
    Pentium 150mhz 96megs of ram, pcmcia 10/100 network card
    OS Debian Jessie (does not support the cmov instruction set)

    machine #2 (durwood)
    Amd Duron processor 1600mhz 2gigs ram, internal 10/100 network card
    OS Ubuntu 18.04 LTS (32-bit)

    both machines setup as a fidonet point, get the exact same error when polling for mail "Error in recv() of first byte of packet header"

    Do you think the machines have something to do with (i.e. this is working on some other system)? I would think it would more likely have to do with the networking configuration. Where/who is the hub (I assume BinkP, you didn't say)? Is there an error on the hub side?

    I have tried increasing the RCVBUF line to 8192 in sockopts.ini thinking just not enough of a buffer but no change.. any ideas?

    You should not normally set the RCVBUF value in sockopts.ini. See this for details: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ctrl/sockopts.ini?view=log
    --
    digital man

    Sling Blade quote #17:
    Charles Bushman: A shovel just makes too goddamned much racket.
    Norco, CA WX: 64.8øF, 85.0% humidity, 2 mph E wind, 0.00 inches rain/24hrs
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Michael2@michael2@FLUXCAP.remove-1k4-this to Digital Man on Fri Oct 23 08:15:36 2020
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Re: SBBS on linux 32-bit
    By: Digital Man to Michael2 on Thu Oct 22 2020 11:20 am

    Re: SBBS on linux 32-bit
    By: Michael2 to All on Thu Oct 22 2020 09:17 am

    ok hope I can explain things so that it makes sense

    have 2 32-bit machines vastly different from each other
    machine #1 (fuji)
    Pentium 150mhz 96megs of ram, pcmcia 10/100 network card
    OS Debian Jessie (does not support the cmov instruction set)

    machine #2 (durwood)
    Amd Duron processor 1600mhz 2gigs ram, internal 10/100 network card
    OS Ubuntu 18.04 LTS (32-bit)

    both machines setup as a fidonet point, get the exact same error when polling for mail "Error in recv() of first byte of packet header"

    Do you think the machines have something to do with (i.e. this is working on some other system)? I would think it would more likely have to do with the networking configuration. Where/who is the hub (I assume BinkP, you didn't say)? Is there an error on the hub side?

    I think 32-bit linux build has something to do with it I am just not sure what? the hub is my mystic system 1:340/201, no error on the hub side. is ftp involved in the transfers? just got to thinking about that.. I dont think ftp is exposed for the point?



    I have tried increasing the RCVBUF line to 8192 in sockopts.ini thinking just not enough of a buffer but no change.. any ideas?

    You should not normally set the RCVBUF value in sockopts.ini. See this for details: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ctrl/sockopts.ini?view=log --
    digital man
    ok.. then is there anything I should change?

    btw this is Synchronet Terminal Server 3.18c SMBLIB 2.61 Compiled Oct 20 2020 08:44:00 with GCC 7.5.0

    ---
    þ Synchronet þ fluxcap.synchro.net:5023 - Portland, OR
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Digital Man@digital.man@vert.synchro.net.remove-62b-this to Michael2 on Fri Oct 23 17:16:23 2020
    From Newsgroup: alt.bbs.synchronet

    To: Michael2
    Re: SBBS on linux 32-bit
    By: Michael2 to Digital Man on Fri Oct 23 2020 08:15 am

    Re: SBBS on linux 32-bit
    By: Digital Man to Michael2 on Thu Oct 22 2020 11:20 am

    Re: SBBS on linux 32-bit
    By: Michael2 to All on Thu Oct 22 2020 09:17 am

    ok hope I can explain things so that it makes sense

    have 2 32-bit machines vastly different from each other
    machine #1 (fuji)
    Pentium 150mhz 96megs of ram, pcmcia 10/100 network card
    OS Debian Jessie (does not support the cmov instruction set)

    machine #2 (durwood)
    Amd Duron processor 1600mhz 2gigs ram, internal 10/100 network card
    OS Ubuntu 18.04 LTS (32-bit)

    both machines setup as a fidonet point, get the exact same error when polling for mail "Error in recv() of first byte of packet header"

    Do you think the machines have something to do with (i.e. this is working on some other system)? I would think it would more likely have to do with the networking configuration. Where/who is the hub (I assume BinkP, you didn't say)? Is there an error on the hub side?

    I think 32-bit linux build has something to do with it I am just not sure what?

    What leads you to think that?

    the hub is my mystic system 1:340/201, no error on the hub side.

    What *does* the log say on the hub's side?

    is
    ftp involved in the transfers? just got to thinking about that.. I dont think ftp is exposed for the point?

    I *think* you're asking about BinkIT, but your question was a bit vague. Anyway, BinkIT uses BinkP (the protocol) exclusively, not FTP.

    I have tried increasing the RCVBUF line to 8192 in sockopts.ini thinking just not enough of a buffer but no change.. any ideas?

    You should not normally set the RCVBUF value in sockopts.ini. See this for details: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/ctrl/sockopts.ini?view=log --

    ok.. then is there anything I should change?

    Not normally. And certainly nothing needs to be changed for BinkIT/BinkP to work.

    btw this is Synchronet Terminal Server 3.18c SMBLIB 2.61 Compiled Oct 20 2020 08:44:00 with GCC 7.5.0

    Okay, that's great. That version is working just fine for BinkIT/BinkP for many, so perhaps the problem is on your hub's end?
    --
    digital man

    Sling Blade quote #9:
    Doyle Hargraves: Morris here is a modern-day poet, kinda like in olden times. Norco, CA WX: 68.9øF, 69.0% humidity, 9 mph NE wind, 0.00 inches rain/24hrs
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113
  • From Michael2@michael2@FLUXCAP.remove-r5q-this to Digital Man on Sun Oct 25 19:16:57 2020
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Re: SBBS on linux 32-bit
    By: Digital Man to Michael2 on Fri Oct 23 2020 05:16 pm

    Okay, that's great. That version is working just fine for BinkIT/BinkP for many, so perhaps the problem is on your hub's end?

    turns out it was the server ... I dont normally reboot that machine ever, but I changed my monitor configuration on the hub machine, and had to reboot, after that it started working.

    sorry I should have thought about that first.

    ---
    þ Synchronet þ fluxcap.synchro.net:5023 - Portland, OR
    --- Synchronet 3.18c-Win32 NewsLink 1.113
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.19c-Linux NewsLink 1.113