Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!news-peer.sprintlink.net!news-peer.sprintlink.net!news.sprintlink.net!sprint!uunet!in3.uu.net!140.142.64.3!news.u.washington.edu!root From: kargl@hotrat.apl.washington.edu (Steven G. Kargl) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Is there a line length limit? (2.2.1) Date: 10 Apr 1997 05:50:29 GMT Organization: University of Washington Lines: 27 Message-ID: <5ihv35$f61@nntp1.u.washington.edu> References: <5ihpck$h8p$1@Mars.mcs.net> NNTP-Posting-Host: ppp-C13.apl.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38838 In article <5ihpck$h8p$1@mars.mcs.net>, font@MCS.COM (Font) writes: > I'm using FreeBSD 2.2.1 and programs which accept input from stdin, > such as cat, won't accept lines longer than about a thousand > characters. If I pipe these characters instead of typing them, > everything works. This happens under /bin/sh and /usr/local/bin/zsh. > Is this something in the kernel? I don't remember ever having run > into this before. Whether I'm typing stdin to awk, doing a "read > line" from /bin/sh, or even doing an fgets(s, sizeof(s), stdin), I run > up against the thousand character barrier when typing in input > (actually I'm scripting it most of the time, but you know what I > mean). > > My ISP uses FreeBSD 3.0 and doesn't exhibit this problem. But I'm not > prepared to go to CURRENT. > cd /usr/include grep BUF stdio.h #define BUFSIZ 1024 /* size of buffer used by setbuf */ -- Steve finger -l kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html