Subj : BinkD 0.9.3h OS/2...
To   : Peter Knapper
From : Bob Jones
Date : Sat Sep 13 2003 05:40 pm

 BJ> I'm running binkd under OS/2.  I know I am at least to 
 BJ> 0.9.4, from Tobi's site.  

 PK> I am now using 0.9.5 (dated 5 Sep 03) from 
 PK>   ftp://happy.carrier.kiev.ua/pub/fidosoft/mailer/binkd
 PK> also from 
 PK>   ftp://ftp.lucky.net/pub/fido/binkd/   (its just one 
 PK> of quite a number of mirrors for the first site), with 

Ok.  I happen to prefer to keep a version of BinkD with the CRC change that 
Tobia put in.  Does the 0.9.5 version have Tobia's CRC patch incorporated?

 PK> just ONE of my regular links having a problem. When I 
 PK> call them using 0.9.5 (or 0.9.4) it fails with a 
 PK> password error, however 0.9.3h using the SAME config 
 PK> files, works fine. Here is a snapshot of the log for 
 PK> 0.9.5 (many parts munged to protect the innocent, the 
 PK> seconds part of the timestamp is real though) -
 PK> + 11 Sep 12:34:39 [1080] addr: 1:234/567@fidonet
 PK> + 11 Sep 12:34:39 [1080] addr: 1:2/3@fidonet
 PK> ? 11 Sep 12:34:40 [1080] rerror: Bad password

I've had some issues along this line also.  I seem to recall that 0.9.3 (or 
some other versions) don't do password checking against *all* A.K.A.'s 
presented.  I believe that was fixed in 0.9.4, and so you may need to ADD a 
line (with password) for associated A.K.A.'s, or the other end may need to do 
something along the same lines.  And I've seen password errors show up (I 
think) from the other end adding an A.K.A. that I corrected by adding a line in 
my control file for the additional A.K.A. (with the correct password)....

....
 BJ> Because I load in the new binkd.txt (or is it 
 PK> binkd.inc) that comes down 
 BJ> the filebone (right after the weekly nodelist updates), 
 BJ> and I use the -C option, I don't know if I would hit 
 BJ> the 40+ day bug....  

 PK> As long as the executable does not end and restart, 
 PK> then I feel the "bug" relates to the OS version itself, 
 PK> not so much to BinkD.

The -C option supposedly "restarts" binkd.  In actuallity, the program does not 
terminate, but it does reread the confiuration files.  Wether it does enough 
re-initialization to get rid of the 4x day problem, I don't know.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
 * Origin: Top Hat 2 BBS (1:343/41)

.