| |
LA5VX > TPK 26.03.97 21:50l 21 Lines 748 Bytes #-10618 (0) @ WW
BID : 335_LA5VX
Read: DL2MDU GUEST
Subj: TPK and sync requests
Path: DB0AAB<DB0SL<DB0RGB<DB0MAK<DB0HOT<DB0LPZ<DB0MER<DB0NHM<DB0SHG<DB0OBK<
DB0CL<DB0CXH<DB0RDB<DB0IL<DB0HHW<DF0HMB<DB0HRO<OZ4BOX<OZ4BBS<OZ4PAC<
OZ2BOT<OZ8BOX<OZ7BBS<OZ6PAC<OZ2PAC<LA9K<LA1E<LA8D<LA7H<LA1B
Sent: 970326/0717Z @:LA1B.BRG.R.NOR.EU #:7757 [Bergen] FBB7.00b $:335_LA5VX
From: LA5VX@LA1B.BRG.R.NOR.EU
To : TPK@WW
LA5VX[F›rde]/TPK 1.83a. Mld: Nr 335. Dato: 26-03-97. Tid: 7:14 UTC
Hello.
I have many nodes between my TPK 1.83a and the PBBS. When my TPK sends a
resync request, it can take a while before the actual headers start
arriving. My TPK is very impatient, so it sends the resync request over
again too early. Along with other users with a long path to the PBBS, this
makes the PBBS starting over and over again on the header-list retransmit.
Does anyone know how I can increase the time my TPK should wait for the
requested headers to arrive? I would like to increase it to may be 30sec, or
even 60 sec. Now I think it is below 20 sec.
From LA5VX Steinar in Foerde, Western LA
Read previous mail | Read next mail
| |
