From owner-freebsd-questions@FreeBSD.ORG Mon Sep 24 11:26:32 2007 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 D1D1816A419 for ; Mon, 24 Sep 2007 11:26:32 +0000 (UTC) (envelope-from david@vizion2000.net) Received: from dns1.vizion2000.net (77-99-36-42.cable.ubr04.chap.blueyonder.co.uk [77.99.36.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8142E13C45B for ; Mon, 24 Sep 2007 11:26:32 +0000 (UTC) (envelope-from david@vizion2000.net) Received: by dns1.vizion2000.net (Postfix, from userid 1007) id BA3091CC46; Mon, 24 Sep 2007 04:41:25 -0700 (PDT) From: David Southwell Organization: Voice and Vision To: freebsd-questions@freebsd.org, Dan Nelson Date: Mon, 24 Sep 2007 04:41:25 -0700 User-Agent: KMail/1.9.7 References: <200709221052.41399.david@vizion2000.net> <200709240409.56605.david@vizion2000.net> <20070924111448.GA87613@owl.midgard.homeip.net> In-Reply-To: <20070924111448.GA87613@owl.midgard.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709240441.25547.david@vizion2000.net> Cc: Subject: Re: stdout -determining size of?? 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: Mon, 24 Sep 2007 11:26:32 -0000 On Monday 24 September 2007 04:14:48 Erik Trulsson wrote: > On Mon, Sep 24, 2007 at 04:09:56AM -0700, David Southwell wrote: > > On Saturday 22 September 2007 12:00:41 Dan Nelson wrote: > > > In the last episode (Sep 22), David Southwell said: > > > > How is the the size of stdout controlled. > > > > > > > > My query comes about because I had a shell running for ages with > > > > unlimited history and found it had gobbled uyp all the space > > > > available to stdout!!! > > > > > > Could you provide the error message that made you think that stdout has > > > a limit? "stdout" could be anything: tty, socket, pipe, file, etc. If > > > you have redirected stdout from a script to a file, like "ls > ls.txt", > > > then it's possible that you filled up a filesystem. > > > > Here is what made me ask the question: > > ------------------------------ > > Weekly output report: > > > > Cleaning up kernel database files: > > > > Rebuilding locate database: > > locate.code: stdout: No space left on device > > Here stdout was almost certainly re-directed to some file on the disk. > Unfortunately the disk was full. > > > Rebuilding whatis database: > > > > -- End of weekly output -- > > ___________________________ > > > > After getting the message I dumped the history and locate.updatedb ran > > without any problem. > > The shells history is probably stored in a file on the disk. > When you removed that file the space became available again. > > > It looks like you simply filled up the filesystem. > Nothing to do with 'the size of stdout'. I understand but how can I manage this? Do you happen to know how to configure history storage? It looks as though I need to choose a filesystem where running run out of space is sufficiently improbable to be inconceivable!! The shell in question is an X Konsole. Thanks again David