From METCALF@crnvma.cern.ch Thu Apr 1 10:15:42 1993 Received: from vm.uni-c.dk by dkuug.dk with SMTP id AA24484 (5.65c8/IDA-1.4.4j for ); Thu, 1 Apr 1993 10:20:31 +0200 Received: from vm.uni-c.dk by vm.uni-c.dk (IBM VM SMTP V2R2) with BSMTP id 3631; Thu, 01 Apr 93 10:20:58 DNT Received: from CERNVM.CERN.CH by vm.uni-c.dk (Mailer R2.07) with BSMTP id 8242; Thu, 01 Apr 93 10:20:57 DNT Received: from CERNVM.CERN.CH (NJE origin METCALF@CERNVM) by CERNVM.CERN.CH (LMail V1.1d/1.7f) with BSMTP id 8957; Thu, 1 Apr 1993 10:21:09 +0200 Resent-Date: Thu, 01 Apr 93 10:19:46 SET Resent-From: Michael Metcalf Resent-To: sc22wg5@dkuug.dk Return-Path: <@CERNVM.CERN.CH:brian@DXCERN.CERN.CH> Received: from CERNVM (NJE origin SMTPIBM@CERNVM) by CERNVM.CERN.CH (LMail V1.1d/1.7f) with BSMTP id 5664; Thu, 1 Apr 1993 08:16:18 +0200 Received: from dxmint.cern.ch by CERNVM.CERN.CH (IBM VM SMTP V2R2) with TCP; Thu, 01 Apr 93 08:16:17 SET Received: by dxcern.cern.ch (5.65/DEC-Ultrix/4.3) id AA07692; Thu, 1 Apr 1993 08:15:48 +0200 From: brian@dxcern.cern.ch (Brian Carpenter CERN-CN) Message-Id: <9304010615.AA07692@dxcern.cern.ch> Subject: you may enjoy this network tale .... (fwd) To: metcalf@crnvma.cern.ch (Michael Metcalf), csen@crnvma.cern.ch, csin@crnvma.cern.ch, fluckiger@vxcrna.cern.ch (Francois Fluckiger), jla@dxcoms.cern.ch (Jacques Altaber) Date: Thu, 1 Apr 1993 08:15:42 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3770 X-Charset: ASCII X-Char-Esc: 29 Thought this might bring a smile to some of you. Mike Date: Fri, 26 Mar 93 23:04:46 HST From: "Joe Dellinger" Subject: The FORTRAN-hating gateway Several months ago we started noticing that (now and again) the network connection to the mainland would become very very slow; this would continue for 10-15 minutes or so, then all would suddenly be well again. A while after this started happening a coworker of mine complained to me that the connection to the mainland _never_ worked anymore. It seems that he had some FORTRAN source that he needed to copy to a machine on the mainland, but he never could because "the network wouldn't stay up long enough for the ftp to complete". Yes, it turned out that the network outages happened whenever he attempted to ftp that _particular_ FORTRAN source file to the mainland. We next tried compressing the file; it copied just fine then (but unfortunately the machine on the mainland had no uncompress program, so it was still no go). Finally we "split" his FORTRAN program up into very small pieces and sent them one at a time. Most of the pieces would copy without trouble, but a few would either not go at all or only go after many _many_ retries. Examining the troublesome pieces, we found they all had one thing in common: they contained comment blocks that began and ended with lines consisting of nothing but capital C's (his preferred FORTRAN commenting style). At this point we started sending e-mail to the network gurus on the mainland asking for help. Of course, they wanted to see an example of our un-ftp-able files, so we mailed some to them... but our mail never got there. Finally we got the bright idea of simply _describing_ what the unsendable files were like. That worked. :-) [Dare I include in this message an example of one of the offending FORTRAN comment blocks? Probably better not!] Eventually we were able to piece together the story. A new gateway had recently been installed between our part of campus and the connection to the mainland. This gateway had GREAT difficulty transmitting packets that contained repeated blocks of capital C's!!!! Just a few such packets would occupy all its energies and prevent most everything else from getting through. At this point we complained to the gateway manufacturer... and were told "Oh, yes, you've hit the repeated C's bug! We know about that already.". Eventually we solved the problem... by buying new gateways from another manufacturer. (In the manufacturer's defense I suppose an inability to propagate FORTRAN programs might be considered a feature by some!) ================== RFC 822 Headers ================== Received: by inet-gw-2.pa.dec.com; id AA05592; Wed, 31 Mar 93 00:00:12 -0800 Received: by vbormc.vbo.dec.com; id AA12943; Wed, 31 Mar 93 09:58:33 +0200 Date: Wed, 31 Mar 93 09:58:30 +0200 Message-Id: <9303310758.AA12943@vbormc.vbo.dec.com>