Subj : possible emsi protocol bug in binkd
To   : All
From : Benny Pedersen
Date : Tue Jan 30 2018 01:47 pm

Hello All!

just in case, if qico runs in xinetd with -a auto, then binkp clients stale, 
this is a bug in binkd

   ----- msged.txt begins -----
Date:   2018-01-29 08:01:20
From:   Benny Pedersen of 2:230/0
To:     Sergey Poziturin
Subj:   hotdoged stopped ...
Attr:   Snt Loc Scn 
Conf:   HOTDOGED                      

Hello Sergey!

18 Oct 2017 09:14, Sergey Poziturin wrote to Benny Pedersen:

 BP>> no more possible for me to use it, it try to dial me, but no files 
 BP>> transfered :/
 SP> How did this happen? 

found the qico bug:

/usr/sbin/qico -a auto
/usr/sbin/qico -a binkp

only the last one works

so binkp protocol clients does not always work with autodetect in qico, so i 
loose emsi on same port as binkp

   ----- qico begins -----
service binkp
{
        disable = no
        protocol = tcp
        flags = IPv4
        port = 24554
        socket_type = stream
        wait = no
        user = xpoint
        server = /usr/sbin/qico 
        server_args = -a binkp
}
   ----- qico ends -----

works :=)

 BP>> wonder if thats same problem i have with aftershook ?
 SP> Hmm. 

hope its not the problem

note 2:230/0 is now supporting ipv6


   ----- msged.txt ends -----

 Regards Benny

.... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.9.76-gentoo-r1 (i686))
 * Origin: I will always keep a PC running CPM 3.0 (2:230/0)

.