topic Re: bash v. ksh history in Operating System - Linux

bash v. ksh history

A. Daniel King_1 — Tue, 20 Jul 2004 16:19:49 GMT

Hi, folks.

From the bash man page, I see:

histappend
If set, the history list is appended to the file named by the value of the HISTFILE variable when the shell exits, rather than overwriting the file.

Q: Is there a way to make bash history save immediately upon execution, like HP-UX ksh, instead of upon exit?

Thanks, all.

Re: bash v. ksh history

Abdul Rahiman — Wed, 21 Jul 2004 12:01:17 GMT

I think that's how the bash_history file works. A work around would be to run the 'history -w' command time-to-time manually to write the history to the history file.
May be you can automate this somehow to achieve the desired result.

regds,
Abdul.

Re: bash v. ksh history

Muthukumar_5 — Wed, 21 Jul 2004 13:14:31 GMT

hai,

bash shell is more efficient and effective that korn shell. It is a advanced one and a superset of all shells.

By default, history command will add the history of commans to $HISTFILE ( $HOME/.bash_history)

You can view the view or execute as #history with out any argument.

bash will store the history of commands upong execution. You can know it as,
# history | tail -10
you will see the history | tail -10 in the list.

If you want to overrite the history file then use history -w or set the histappend shell variable as 1 in .bash_profile file.

Re: bash v. ksh history

Steven E. Protter — Wed, 21 Jul 2004 13:20:21 GMT

I've noticed there is a lag in updating the .bash_history file.

For example

Two root sessions open:

do a few commands in session 1.

go to session 2 and those commands are not available in session 2.

It gets annoying. I've played with this for some time but not been able to get immediate update.

SEP

Re: bash v. ksh history

A. Daniel King_1 — Thu, 22 Jul 2004 15:26:11 GMT

export PS1='$(history -w)\w\$ '

Did a near enough approximation.

Thanks all!