From owner-freebsd-questions@FreeBSD.ORG Sat Sep 13 16:26:57 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D852106567A for ; Sat, 13 Sep 2008 16:26:57 +0000 (UTC) (envelope-from ws@au.dyndns.ws) Received: from ipmail05.adl2.internode.on.net (ipmail05.adl2.internode.on.net [203.16.214.145]) by mx1.freebsd.org (Postfix) with ESMTP id B01DF8FC0C for ; Sat, 13 Sep 2008 16:26:56 +0000 (UTC) (envelope-from ws@au.dyndns.ws) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsQAANKEy0iWZWdv/2dsb2JhbAAItC2BZA X-IronPort-AV: E=Sophos;i="4.32,394,1217773800"; d="scan'208";a="205090627" Received: from ppp103-111.static.internode.on.net (HELO [192.168.1.157]) ([150.101.103.111]) by ipmail05.adl2.internode.on.net with ESMTP; 14 Sep 2008 01:56:53 +0930 From: Wayne Sierke To: Jeff Haran In-Reply-To: <57AC2FA1761300418C7AB8F3EA493C9701E0E2B6@HQ-EXCH-5.corp.brocade.com> References: <57AC2FA1761300418C7AB8F3EA493C9701E0DF76@HQ-EXCH-5.corp.brocade.com> <1220688694.2581.13.camel@predator-ii.buffyverse> <57AC2FA1761300418C7AB8F3EA493C9701E0E2B6@HQ-EXCH-5.corp.brocade.com> Content-Type: text/plain Date: Sun, 14 Sep 2008 01:56:51 +0930 Message-Id: <1221323211.2581.105.camel@predator-ii.buffyverse> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: RE: how do I disable the generation of XOFFs when using tip over aserial port to another device X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2008 16:26:57 -0000 On Mon, 2008-09-08 at 10:50 -0700, Jeff Haran wrote: > Wayne, > > Thanks for the response. After I sent the original email, I found the > tandem variable in the tip source code and toggling it off did indeed > disable the generation of XOFFs. It would have been easier if tandem had > been documented in the 6.3 man pages. > > It would also be convenient if there was some way to set these tip > varibles non-interactively (e.g. via a command line option, .rc file or > some such thing). I am using tip in an expect script to automate a test > case and coding the expect script to generate the ~s escape sequence to > turn tandem off was something less than straight forward. > > Jeff Haran Further to my earlier reply... tip(1) does in fact support configuration through ~/.tiprc and adding: !tandem to it should work to disable XON/XOFF generation, too. Perusing the source reveals that cu(1) also uses that configuration file since tip and cu both call the same routine - vinit() - to initialise their variables and that's where ~/.tiprc is read. Not mentioned in the cu(1) man page, however, so that's another PR coming. Wayne