As Black Panther mentioned, Linux 32 bit via the old binkp
or via mis2 binkp (same result) can't fidopoll, it yields the
errors:

FIDOPOLL Version 1.12 A36

Scanning 21:1/145
Queued 0 files (0 bytes) to 21:1/145
Polling BINKP node 21:1/145
Connecting to bcw142.zapto.org:24556
Connected
Socket Write error 25
Socket Write error 25
Socket Write error 25
Socket Write error 25
Socket read error 25
Socket Write error 25
Socket read error 25
Socket Write error 25
Socket read error 25
Socket Write error 25
Receiving: 00000003.sa0 (61,003 bytes)
Socket read error 25

So that's two sources with the same error. x64 Linux works fine,
so something in the mys112a36_l32 isn't right.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 10/31/17, bcw142 said the following...

As Black Panther mentioned, Linux 32 bit via the old binkp
or via mis2 binkp (same result) can't fidopoll, it yields the
errors:

I was actually having the issues with Linux 64 bit over here...

It also seemed to only maintain a 'fidopoll.log' file of 5k in size. That wasn't even enough to view the polling of two systems...

I've downgraded the fidopoll program to the previous A36 release so that polling could continue.


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A36 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

As Black Panther mentioned, Linux 32 bit via the old binkp
or via mis2 binkp (same result) can't fidopoll, it yields the
errors:

From the logs you guys are posting, its not showing any failures. You are posting debug logging.

Are you saying the files were not sent or corrupt?

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

It also seemed to only maintain a 'fidopoll.log' file of 5k in size. That wasn't even enough to view the polling of two systems...

This is not true, it doesn't maintain any log size. The logging code wasn't touched between versions so that is odd.

--- Mystic BBS v1.12 A36 2017/10/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 10/31/17, g00r00 said the following...

It also seemed to only maintain a 'fidopoll.log' file of 5k in size. wasn't even enough to view the polling of two systems...

This is not true, it doesn't maintain any log size. The logging code wasn't touched between versions so that is odd.

It is odd... As soon as I put the first A36 version of Fidopoll back in, the log file started to grow again...

It is Halloween, so there may be a hungry zombie in the system somewhere... ;)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS(RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A36 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

It is odd... As soon as I put the first A36 version of Fidopoll back in, the log file started to grow again...

Its very odd. I do see that behavior too but I haven't changed anything!

It is Halloween, so there may be a hungry zombie in the system somewhere... ;)

Haha that sounds about as logical as anything I was thinking lol

I'll look into it.

--- Mystic BBS v1.12 A36 2017/11/01 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)