From: Monty Scroggins <c-Monty.Scroggins@wcom.com>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-workers@sunsite.dk
Subject: RE: zsh: fatal error: out of memory
Date: Wed, 12 Sep 2001 11:11:50 -0500 [thread overview]
Message-ID: <FLEKKKDFJJDCBMPOEGGPIEOOCBAA.c-Monty.Scroggins@wcom.com> (raw)
In-Reply-To: <1010912153118.ZM25812@candle.brasslantern.com>
My mistake.. the file size should have been 168560 bytes
not k bytes...
By "type of problem", I assumed the problem is in the sheer
size of the history file. I did not realize the format
is different than what zsh expects.
The shell history file would have been created from ksh.
It looks like ksh is used as a default shell for all the
users on that box..
Monty
-----Original Message-----
} The .sh_history file is 168560k and 7952 lines..
^
Really? That would be 21700 bytes per line,
average, which seems a bit unbelievable.
} but maybe zsh should handle this type of problem..
The question is, what is "this type". I think it's more likely that the
problem is:
} each line starts with one or more <nul> characters followed
} by the command strings..
Zsh assumes that a history file consists only of the commands themselves;
even when `extended_history' is set, it inserts time stamps in `: ...;'
form so that they can be interpreted as commands.
Any idea which shell created the .sh_history file in the first place?
prev parent reply other threads:[~2001-09-12 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 18:26 Monty Scroggins
2001-09-11 14:07 ` Bart Schaefer
2001-09-11 22:22 ` Monty Scroggins
2001-09-11 23:19 ` Bart Schaefer
2001-09-12 14:10 ` Monty Scroggins
2001-09-12 15:31 ` Bart Schaefer
2001-09-12 16:08 ` Oliver Kiddle
2001-09-12 21:13 ` Bart Schaefer
2001-09-13 5:32 ` Borsenkow Andrej
2001-09-12 16:11 ` Monty Scroggins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FLEKKKDFJJDCBMPOEGGPIEOOCBAA.c-Monty.Scroggins@wcom.com \
--to=c-monty.scroggins@wcom.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).