Discussion:
Binkd 1.1a-52
(too old to reply)
Tommi Koivula
2014-08-04 06:36:08 UTC
Permalink
Hi All,

Binkd 1.1a-52 server will exit after the first call if started with -s.

04 Aug 10:25:59 [7475] BEGIN, binkd/1.1a-52/OS2 -vv -s -C binkd.cfg
04 Aug 10:25:59 [7475] created binkd.pid
04 Aug 10:25:59 [7475] servmgr started
- 04 Aug 10:25:59 [7475] servmgr listen on *:24554
- 04 Aug 10:26:16 [7475] incoming from 91.155.105.204 (4801)
04 Aug 10:26:17 [7475] started server #1, id=7488
04 Aug 10:26:17 [7488] binkp init done, socket # is 5
+ 04 Aug 10:26:17 [7488] incoming session with
a91-155-105-204.elisa-laajakaista.fi [91.155.105.204]
04 Aug 10:26:17 [7488] send message NUL OPT
CRAM-MD5-3616d78b1a23d74a6439c98e6135ccee
04 Aug 10:26:17 [7488] send message NUL SYS f0.n22.z2.binkp.net
04 Aug 10:26:17 [7488] send message NUL ZYZ Tommi Koivula
04 Aug 10:26:17 [7488] send message NUL LOC Lake Ylo, Finland
04 Aug 10:26:17 [7488] send message NUL NDL IBN,ICM
04 Aug 10:26:17 [7488] send message NUL TIME Mon, 4 Aug 2014 10:26:17 +0300
04 Aug 10:26:17 [7488] send message NUL VER binkd/1.1a-52/OS2 binkp/1.1
? 04 Aug 10:26:17 [7488] recv: Connection reset by peer
+ 04 Aug 10:26:17 [7488] done (?, failed, S/R: 0/0 (0/0 bytes))
04 Aug 10:26:17 [7488] processing kill list
04 Aug 10:26:17 [7488] binkp deinit done...
04 Aug 10:26:17 [7488] session closed, quitting...
04 Aug 10:26:17 [7488] downing server...
04 Aug 10:26:17 [7488] Closing server socket # 3
04 Aug 10:26:17 [7488] bsy_remove_all: done
04 Aug 10:26:17 [7475] rc(7488)=0
? 04 Aug 10:26:17 [7475] servmgr select(): No children
04 Aug 10:26:17 [7475] downing servmgr...
04 Aug 10:26:17 [7475] Closing server socket # 3
04 Aug 10:26:17 [7475] bsy_remove_all: done

'Tommi
Tommi Koivula
2014-08-07 06:00:11 UTC
Permalink
* Originally in BINKD
* Crossposted in RU.BINKD

Monday August 04 2014 10:36, Tommi Koivula wrote to All:

TK>
TK> Binkd 1.1a-52 server will exit after the first call if started with
TK> -s.
TK>

The same thing is happening with 1.0.3 too. Is this intentional change? If so,
I have to change something. Until then, I'll stay with -49.

'Tommi
Pavel Gulchouck
2014-08-09 12:58:56 UTC
Permalink
Hi Tommi!

04 Aug 14, Tommi Koivula ==> All:

TK> Binkd 1.1a-52 server will exit after the first call if started with -s.

Sorry for this.
Please try 1.1a-53.

Lucky carrier,
Pavel
aka ***@gul.kiev.ua
Tommi Koivula
2014-08-10 06:13:49 UTC
Permalink
Hello Pavel!

09 Aug 14 16:58, you wrote to me:

PG> 04 Aug 14, Tommi Koivula ==> All:

TK>> Binkd 1.1a-52 server will exit after the first call if started
TK>> with -s.

PG> Sorry for this.
PG> Please try 1.1a-53.

I will. Thanks!

'Tommi
Tommi Koivula
2014-08-10 14:38:23 UTC
Permalink
Saturday August 09 2014 16:58, Pavel Gulchouck wrote to Tommi Koivula:

PG> 04 Aug 14, Tommi Koivula ==> All:
PG>
TK>> Binkd 1.1a-52 server will exit after the first call if started
TK>> with -s.
PG>
PG> Sorry for this.
PG> Please try 1.1a-53.

Seems to fixed!

But another problem with -54. When initiating a poll with
"binkd2e.exe -pP 2:221/360 binkd,cfg",
binkd will hog all the cpu in a single core athlon xp os/2 system. This is
happening also with the windows version, only that it hogs 50% cpu in my 2-cpu
xeon computer.

'Tommi

Loading...