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.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"