Xref: utzoo comp.unix.questions:16390 comp.bugs.sys5:1143 comp.unix.xenix:7662 comp.unix.ultrix:1733
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!shlump.nac.dec.com!riscy.dec.com!croton.dec.com!frank
From: frank@croton.dec.com (Frank Wortner)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.xenix,comp.unix.ultrix
Subject: Re: ksh - no space error message
Message-ID: <1486@riscy.dec.com>
Date: 18 Sep 89 13:42:47 GMT
References: <658@tijc02.UUCP>
Sender: news@riscy.dec.com
Followup-To: comp.unix.questions
Distribution: usa
Organization: Digital Equipment Corporation, NYC
Lines: 18


In article <658@tijc02.UUCP>, cgh018@tijc02.UUCP (Calvin Hayden ) writes:

> Has anyone using ksh seen the following error:
> 
> ksh: no space

... may or may not have anything to do with the problem ...

Check those "dot" files!  Someone once asked me to figure out why ksh
suddenly seemed to start taking forever to start.  I did an "ls -la"
and found that the ".history" file was 12Meg!  (To this day I have no
idea what caused this.)

Corrupted "dot" files can cause programs to behave in strange ways.

Regards,
					Frank