Date: Sun, 14 Sep 2008 01:56:51 +0930 From: Wayne Sierke <ws@au.dyndns.ws> To: Jeff Haran <jharan@Brocade.COM> Cc: freebsd-questions@freebsd.org Subject: RE: how do I disable the generation of XOFFs when using tip over aserial port to another device Message-ID: <1221323211.2581.105.camel@predator-ii.buffyverse> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1221323211.2581.105.camel>