public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tim Kruse <irrlicht2c@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: bash_history
Date: Tue, 7 Mar 2006 03:46:31 +0100	[thread overview]
Message-ID: <9p8vd3-37s.ln1@news.irrlicht.homelinux.net> (raw)
In-Reply-To: 1141691942.11274.19.camel@parker.babysnakes.org

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

* On 07.03.2006 Haim Ashkenazi wrote:

>> I am wondering what do I need to config so that when a user or root
>> type reboot the commands typed before a saved in bash_history and also
>> when the user or root don' type anything but just press combination of
>> keys ctrl+alt+del?
> when you press reboot the shell process dies, so it doesn't save the
> history. if you want to save history you have to exit the shell and then
> login and enter reboot, or press ctrl+alt+del.

 I love zsh ;-)

,-----
| % setopt | grep -i "append.*history"
| incappendhistory
| % man zshoptions | col -b | grep -A 4 APPEND_HISTORY
|     APPEND_HISTORY <D>
|         If this is set, zsh sessions will append their history  list  to
|         the  history file, rather than overwrite it. Thus, multiple par-
|         allel zsh sessions will all have their history  lists  added  to
|         the history file, in the order they are killed.
|--
|     INC_APPEND_HISTORY
|         This options works like APPEND_HISTORY except that  new  history
|         lines  are added to the $HISTFILE incrementally (as soon as they
|         are entered), rather than waiting until  the  shell  is  killed.
|         The  file  is periodically trimmed to the number of lines speci-
|         fied by $SAVEHIST, but can exceed this value between  trimmings.
`-----

 So long,
tkr

-- 
"There are some good people in it, but the orchestra as a whole is equivalent
to a gang bent on destruction."
-- John Cage, composer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-03-07  2:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07  0:17 [gentoo-user] bash_history Goran Maksimović
2006-03-07  0:39 ` Haim Ashkenazi
2006-03-07  2:46   ` Tim Kruse [this message]
2006-03-07  8:25     ` [gentoo-user] bash_history Haim Ashkenazi
2006-03-07 22:58     ` Harry Putnam
2006-03-18  9:17       ` Tim Kruse
2006-03-18 23:07         ` Neil Bothwick
2006-03-19  8:18           ` Tim Kruse
2006-03-19 16:06             ` Neil Bothwick
2006-03-19 17:37             ` Octavio Ruiz (Ta^3)
2006-03-20  9:31               ` Neil Bothwick
2006-03-18  9:24       ` Tim Kruse
2006-03-07 10:10   ` [gentoo-user] bash_history Matteo Lanza
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07  8:42 [gentoo-user] bash_history Goran Maksimoviæ
2006-03-07 19:39 ` Simon Kellett
2006-03-08 12:14 Goran Maksimoviæ

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=9p8vd3-37s.ln1@news.irrlicht.homelinux.net \
    --to=irrlicht2c@gmx.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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