From: Eric Malkowski <eric@bvwireless.net>
To: buildroot@busybox.net
Subject: [Buildroot] Shell history w/ ASH spans multiple ash instances
Date: Thu, 19 Feb 2009 00:12:32 -0500 [thread overview]
Message-ID: <499CEA40.1000907@bvwireless.net> (raw)
Hi all-
In the past, if multiple shells were started on console and ssh for
instance, the command history was always unique per shell instance.
It seems the "ash" shell now likes to save history in /root/.ash_history
periodically? and at odd points, command history from one shell starts
showing up in another.
This gets very annoying when I'm trying to recall the last command I
CTRL-C'd out of for instance, but I get the "top" of the history from
some "other" shell instance.
I tried making /etc/profile and /root/.bashrc NOT set the env vars
HISTSIZE and HISTFILESIZE, but ash still keeps writing stuff to
/root/.ash_history and "polluting" history for my various shell instances.
I'm tempted to turn off CONFIG_FEATURE_EDITING_HISTORY and
CONFIG_FEATURE_EDITING_SAVEHISTORY in the busybox config, but I still
want to be able to use up-arrow in shells to get history -- I just don't
want it being saved to .ash_history and loaded into the history of other
shells -- just saving history to .ash_history when a shell exits is
fine, it's this "live updating" of it I'd like to get rid of.
Any advice greatly appreciated.
BTW: I'm using busybox 1.13.2 per stock buildroot config.
-Eric Malkowski
next reply other threads:[~2009-02-19 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 5:12 Eric Malkowski [this message]
2009-02-19 9:58 ` [Buildroot] Shell history w/ ASH spans multiple ash instances Peter Korsgaard
2009-02-19 14:49 ` Eric Malkowski
2009-02-19 15:14 ` Peter Korsgaard
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=499CEA40.1000907@bvwireless.net \
--to=eric@bvwireless.net \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox