From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: webserver stalls [was Re: bug in (linux) slattach] Date: 21 Oct 2002 12:55:03 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1035194100.1634.96.camel@cool> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8pO8VlKzn2xLqt0f658w" Return-path: In-Reply-To: List-Id: To: jb1@btstream.com Cc: Linux-8086 --=-8pO8VlKzn2xLqt0f658w Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > On 20 Oct 2002, Harry Kalogirou wrote: >=20 > > > On 19 Oct 2002, Harry Kalogirou wrote: > ... > > As I suspected, misconfigued line. Configure your like this : > >=20 > > intr =3D ; quit =3D ; erase =3D ; kill =3D = ; eof =3D > > ; > > eol =3D ; eol2 =3D ; start =3D ; stop =3D ;= susp =3D > > ; > > rprnt =3D ; werase =3D ; lnext =3D ; flush =3D ; > > min =3D 1; time =3D 0; > > -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts > > ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon > > -ixoff > > -iuclc -ixany -imaxbel > > -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 > > bs0 vt0 > > ff0 > > -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tosto= p > > -echoprt -echoctl -echoke > > =20 > >=20 > > Basicaly the above configuration is done by the -L parameter of > > slattach, except the -crtscts. What I do just to be sure is : > >=20 > > # slattach -p [c]slip -L -e /dev/ttyS0 > > # stty -F /dev/ttyS0 -crtscts > > # slattach -p [c]slip -s 4800 -m /dev/ttyS0 & >=20 > I did as you suggested (with one exception), confirmed that the settings=20 > were exactly like yours, and found *no* difference; the 99-byte webpage=20 > file works, the 100-byte byte webpage files don't. The exception was: > stty 4800 -F /dev/ttyS0 -crtscts > because my slattach program doesn't seem to change the baud rate. Also,=20 > I still getting frequent seemingly-random errors when I ping the ELKS box= . Mmm.. weird.. I probably got you tired with all this but can you try and see if the failures are realy random? A good aid at this the -p parameter of ping. I'm just convinsed that there is a problem after the packets leave ELKS. Harry --=-8pO8VlKzn2xLqt0f658w Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9s87yXrjIZPA34x8RAr8GAJ4/X0de4DULmpnew4pvwEoF4qjlSgCeLmyv 5/xDCPmMnGLx1HYxVeBRAfY= =wsWr -----END PGP SIGNATURE----- --=-8pO8VlKzn2xLqt0f658w--