The "problem" seems to be unique to nodes running ARcluster
software. Try the same thing with a node using one of the
other varieties (CLX, Pavilion, etc.) and the symptom does
not appear.
I would wager that ARCluster gets itself in a CR/LF loop if
one asks for more data than it has in the queue. Do a
SH/DX/10 and you're OK ... do a SH/DX/100 and you're sure to
crash.
73,
... Joe Subich, W8IK/4
<W8IK@ARRL.NET>
> -----Original Message-----
> From: owner-writelog@contesting.com
> [mailto:owner-writelog@contesting.com]On Behalf Of Marty Tippin
> Sent: Monday, February 28, 2000 10:02 PM
> To: w5xd@alum.mit.edu
> Cc: writelog@contesting.com
> Subject: Re: [WriteLog] RE: Fix For Packet Problem before ARRL DX PHONE
> Contest???
>
>
>
> Hi Wayne -
>
> I suppose you've been inundated by now, but here's my 2 cents worth...
>
> Here's how to reproduce the problem:
> 1. Log in to packet cluster via telnet node (I used the wu3v node
> specifically - dxc.wu3v.net) - don't know if it's specific to telnet or
> not, but KG0US and I have both seen the problem and are using telnet.
> 2. do "SH/DX/100"
>
>
--
WWW: http://www.contesting.com/writelog
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|