Why is .bash_history periodically wiped? The Next CEO of Stack OverflowWhy does iterm2 close new sessions immediately?Why does Terminal ignore capital “B”?Why does shasum generate non-standard hashes?In iTerm, why is a command shell's command not picking up things on my $PATH?Odd bug in iTerm — Why is my name wrong?Why bash history on my mac won't save?I deleted .bash_history, now history isn't saved anymore (although I re-created it)Why ALT+. (last parameter) does not work in Bash?iTerm spits out text every time I start a new session - why, and how to stop it?How are command line commands stored in .bash_history?

Finitely generated matrix groups whose eigenvalues are all algebraic

Is this a new Fibonacci Identity?

Is it "common practice in Fourier transform spectroscopy to multiply the measured interferogram by an apodizing function"? If so, why?

Is it reasonable to ask other researchers to send me their previous grant applications?

How to show a landlord what we have in savings?

My boss doesn't want me to have a side project

Does int main() need a declaration on C++?

How to compactly explain secondary and tertiary characters without resorting to stereotypes?

Gauss' Posthumous Publications?

How to pronounce fünf in 45

Calculate the Mean mean of two numbers

Is the offspring between a demon and a celestial possible? If so what is it called and is it in a book somewhere?

Was the Stack Exchange "Happy April Fools" page fitting with the 90s code?

How to coordinate airplane tickets?

Could a dragon use hot air to help it take off?

What does this strange code stamp on my passport mean?

Are British MPs missing the point, with these 'Indicative Votes'?

How dangerous is XSS

Ising model simulation

Can a PhD from a non-TU9 German university become a professor in a TU9 university?

What is the difference between 'contrib' and 'non-free' packages repositories?

Gödel's incompleteness theorems - what are the religious implications?

Find the majority element, which appears more than half the time

That's an odd coin - I wonder why



Why is .bash_history periodically wiped?



The Next CEO of Stack OverflowWhy does iterm2 close new sessions immediately?Why does Terminal ignore capital “B”?Why does shasum generate non-standard hashes?In iTerm, why is a command shell's command not picking up things on my $PATH?Odd bug in iTerm — Why is my name wrong?Why bash history on my mac won't save?I deleted .bash_history, now history isn't saved anymore (although I re-created it)Why ALT+. (last parameter) does not work in Bash?iTerm spits out text every time I start a new session - why, and how to stop it?How are command line commands stored in .bash_history?










3















This is the second time it's happened.
I just tried grep-ing some historical commands and came up empty. a look at my bash history shows that it's practically empty. Like it's been wiped clean.
I use iTerm2 and on MacOS 10.13.6.
I see there's a .bash_sessions directory with some sessions saved but I guess this is probably an iTerm2 thing to preserve sessions for some reason or another.










share|improve this question






















  • unix.stackexchange.com/questions/163371/…

    – JBis
    Mar 25 at 11:32















3















This is the second time it's happened.
I just tried grep-ing some historical commands and came up empty. a look at my bash history shows that it's practically empty. Like it's been wiped clean.
I use iTerm2 and on MacOS 10.13.6.
I see there's a .bash_sessions directory with some sessions saved but I guess this is probably an iTerm2 thing to preserve sessions for some reason or another.










share|improve this question






















  • unix.stackexchange.com/questions/163371/…

    – JBis
    Mar 25 at 11:32













3












3








3


1






This is the second time it's happened.
I just tried grep-ing some historical commands and came up empty. a look at my bash history shows that it's practically empty. Like it's been wiped clean.
I use iTerm2 and on MacOS 10.13.6.
I see there's a .bash_sessions directory with some sessions saved but I guess this is probably an iTerm2 thing to preserve sessions for some reason or another.










share|improve this question














This is the second time it's happened.
I just tried grep-ing some historical commands and came up empty. a look at my bash history shows that it's practically empty. Like it's been wiped clean.
I use iTerm2 and on MacOS 10.13.6.
I see there's a .bash_sessions directory with some sessions saved but I guess this is probably an iTerm2 thing to preserve sessions for some reason or another.







terminal bash iterm






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 25 at 10:33









Dark Star1Dark Star1

249211




249211












  • unix.stackexchange.com/questions/163371/…

    – JBis
    Mar 25 at 11:32

















  • unix.stackexchange.com/questions/163371/…

    – JBis
    Mar 25 at 11:32
















unix.stackexchange.com/questions/163371/…

– JBis
Mar 25 at 11:32





unix.stackexchange.com/questions/163371/…

– JBis
Mar 25 at 11:32










1 Answer
1






active

oldest

votes


















6














There can be multiple reasons as to why this happens - I'll try to outline how it works below.



However, I can say that the other answer you have received here is not correct. HISTFILESIZE and HISTSIZE will not cause your history to "sometimes" being entirely wiped out or almost wiped out. Only by setting them to 0 you would get nothing in the files - but it would happen every time, and not by chance. In addition, what you describe with the file being "almost wiped out" cannot happen due to it being set to 0.



You're actually on to the right thing yourself by mentioning .bash_sessions. That is not an iTerm2 "thing", but rather how it works by default on a standard macOS install. Apple has built-in per-session history on top of a regular bash install.



This means that if you have multiple terminals running (for example multiple tabs), each of those will have a seperate history tracked in .bash_sessions. If you reboot your Mac and the terminal windows are restored, you'll find that each still have their own history - and only their own history.



When you close down a bash session, Apple's system will merge the history for that specific session into the global .bash_history file. Then when you open a new terminal (and thus bash session), it will start with that merged history containing history from potentially multiple sessions.



This is all handled by the /etc/bashrc_Apple_Terminal script.



Now that you know how it works, here are some possible causes for what you're seeing:



  • You may accidentially have removed the history yourself (history -c)


  • Your Mac could be infected with malware and/or hacked, and someone else is removing your .bash_history file


  • You have software installed that periodically empties/removes .bash_history


These reasons are not that likely, I would say.



Now there's one last possible cause:



There's a known race-condition in handling the bash histories. If you close down multiple bash sessions at once (for example closing down a terminal window with multiple tabs), you might loose part of or the whole history.



This happens if the computer is "slow" while reading/writing parts of the history. Basically how it works is that your currently history is read, the file is deleted/moved away, and a new file is created, where all the history lines are written to. If this process is running multiple times at the same time, you might see that one process removes the old history, the other process read an empty history, then the first process writes out the whole history again, and then the other process deletes that and writes out a very short history containing only few recent lines - as it didn't read anything in. This bug shows up as exactly what you have described.



The fix is simply to close one bash session at a time to let the system have time to write out everything correctly.






share|improve this answer























  • Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

    – Dark Star1
    Mar 25 at 14:18











  • Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

    – QuickishFM
    Mar 25 at 14:31











  • This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

    – Dark Star1
    Mar 25 at 15:16











  • As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

    – jpa
    Mar 25 at 19:18











  • The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

    – jksoegaard
    Mar 25 at 19:42











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "118"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f354746%2fwhy-is-bash-history-periodically-wiped%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














There can be multiple reasons as to why this happens - I'll try to outline how it works below.



However, I can say that the other answer you have received here is not correct. HISTFILESIZE and HISTSIZE will not cause your history to "sometimes" being entirely wiped out or almost wiped out. Only by setting them to 0 you would get nothing in the files - but it would happen every time, and not by chance. In addition, what you describe with the file being "almost wiped out" cannot happen due to it being set to 0.



You're actually on to the right thing yourself by mentioning .bash_sessions. That is not an iTerm2 "thing", but rather how it works by default on a standard macOS install. Apple has built-in per-session history on top of a regular bash install.



This means that if you have multiple terminals running (for example multiple tabs), each of those will have a seperate history tracked in .bash_sessions. If you reboot your Mac and the terminal windows are restored, you'll find that each still have their own history - and only their own history.



When you close down a bash session, Apple's system will merge the history for that specific session into the global .bash_history file. Then when you open a new terminal (and thus bash session), it will start with that merged history containing history from potentially multiple sessions.



This is all handled by the /etc/bashrc_Apple_Terminal script.



Now that you know how it works, here are some possible causes for what you're seeing:



  • You may accidentially have removed the history yourself (history -c)


  • Your Mac could be infected with malware and/or hacked, and someone else is removing your .bash_history file


  • You have software installed that periodically empties/removes .bash_history


These reasons are not that likely, I would say.



Now there's one last possible cause:



There's a known race-condition in handling the bash histories. If you close down multiple bash sessions at once (for example closing down a terminal window with multiple tabs), you might loose part of or the whole history.



This happens if the computer is "slow" while reading/writing parts of the history. Basically how it works is that your currently history is read, the file is deleted/moved away, and a new file is created, where all the history lines are written to. If this process is running multiple times at the same time, you might see that one process removes the old history, the other process read an empty history, then the first process writes out the whole history again, and then the other process deletes that and writes out a very short history containing only few recent lines - as it didn't read anything in. This bug shows up as exactly what you have described.



The fix is simply to close one bash session at a time to let the system have time to write out everything correctly.






share|improve this answer























  • Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

    – Dark Star1
    Mar 25 at 14:18











  • Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

    – QuickishFM
    Mar 25 at 14:31











  • This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

    – Dark Star1
    Mar 25 at 15:16











  • As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

    – jpa
    Mar 25 at 19:18











  • The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

    – jksoegaard
    Mar 25 at 19:42















6














There can be multiple reasons as to why this happens - I'll try to outline how it works below.



However, I can say that the other answer you have received here is not correct. HISTFILESIZE and HISTSIZE will not cause your history to "sometimes" being entirely wiped out or almost wiped out. Only by setting them to 0 you would get nothing in the files - but it would happen every time, and not by chance. In addition, what you describe with the file being "almost wiped out" cannot happen due to it being set to 0.



You're actually on to the right thing yourself by mentioning .bash_sessions. That is not an iTerm2 "thing", but rather how it works by default on a standard macOS install. Apple has built-in per-session history on top of a regular bash install.



This means that if you have multiple terminals running (for example multiple tabs), each of those will have a seperate history tracked in .bash_sessions. If you reboot your Mac and the terminal windows are restored, you'll find that each still have their own history - and only their own history.



When you close down a bash session, Apple's system will merge the history for that specific session into the global .bash_history file. Then when you open a new terminal (and thus bash session), it will start with that merged history containing history from potentially multiple sessions.



This is all handled by the /etc/bashrc_Apple_Terminal script.



Now that you know how it works, here are some possible causes for what you're seeing:



  • You may accidentially have removed the history yourself (history -c)


  • Your Mac could be infected with malware and/or hacked, and someone else is removing your .bash_history file


  • You have software installed that periodically empties/removes .bash_history


These reasons are not that likely, I would say.



Now there's one last possible cause:



There's a known race-condition in handling the bash histories. If you close down multiple bash sessions at once (for example closing down a terminal window with multiple tabs), you might loose part of or the whole history.



This happens if the computer is "slow" while reading/writing parts of the history. Basically how it works is that your currently history is read, the file is deleted/moved away, and a new file is created, where all the history lines are written to. If this process is running multiple times at the same time, you might see that one process removes the old history, the other process read an empty history, then the first process writes out the whole history again, and then the other process deletes that and writes out a very short history containing only few recent lines - as it didn't read anything in. This bug shows up as exactly what you have described.



The fix is simply to close one bash session at a time to let the system have time to write out everything correctly.






share|improve this answer























  • Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

    – Dark Star1
    Mar 25 at 14:18











  • Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

    – QuickishFM
    Mar 25 at 14:31











  • This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

    – Dark Star1
    Mar 25 at 15:16











  • As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

    – jpa
    Mar 25 at 19:18











  • The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

    – jksoegaard
    Mar 25 at 19:42













6












6








6







There can be multiple reasons as to why this happens - I'll try to outline how it works below.



However, I can say that the other answer you have received here is not correct. HISTFILESIZE and HISTSIZE will not cause your history to "sometimes" being entirely wiped out or almost wiped out. Only by setting them to 0 you would get nothing in the files - but it would happen every time, and not by chance. In addition, what you describe with the file being "almost wiped out" cannot happen due to it being set to 0.



You're actually on to the right thing yourself by mentioning .bash_sessions. That is not an iTerm2 "thing", but rather how it works by default on a standard macOS install. Apple has built-in per-session history on top of a regular bash install.



This means that if you have multiple terminals running (for example multiple tabs), each of those will have a seperate history tracked in .bash_sessions. If you reboot your Mac and the terminal windows are restored, you'll find that each still have their own history - and only their own history.



When you close down a bash session, Apple's system will merge the history for that specific session into the global .bash_history file. Then when you open a new terminal (and thus bash session), it will start with that merged history containing history from potentially multiple sessions.



This is all handled by the /etc/bashrc_Apple_Terminal script.



Now that you know how it works, here are some possible causes for what you're seeing:



  • You may accidentially have removed the history yourself (history -c)


  • Your Mac could be infected with malware and/or hacked, and someone else is removing your .bash_history file


  • You have software installed that periodically empties/removes .bash_history


These reasons are not that likely, I would say.



Now there's one last possible cause:



There's a known race-condition in handling the bash histories. If you close down multiple bash sessions at once (for example closing down a terminal window with multiple tabs), you might loose part of or the whole history.



This happens if the computer is "slow" while reading/writing parts of the history. Basically how it works is that your currently history is read, the file is deleted/moved away, and a new file is created, where all the history lines are written to. If this process is running multiple times at the same time, you might see that one process removes the old history, the other process read an empty history, then the first process writes out the whole history again, and then the other process deletes that and writes out a very short history containing only few recent lines - as it didn't read anything in. This bug shows up as exactly what you have described.



The fix is simply to close one bash session at a time to let the system have time to write out everything correctly.






share|improve this answer













There can be multiple reasons as to why this happens - I'll try to outline how it works below.



However, I can say that the other answer you have received here is not correct. HISTFILESIZE and HISTSIZE will not cause your history to "sometimes" being entirely wiped out or almost wiped out. Only by setting them to 0 you would get nothing in the files - but it would happen every time, and not by chance. In addition, what you describe with the file being "almost wiped out" cannot happen due to it being set to 0.



You're actually on to the right thing yourself by mentioning .bash_sessions. That is not an iTerm2 "thing", but rather how it works by default on a standard macOS install. Apple has built-in per-session history on top of a regular bash install.



This means that if you have multiple terminals running (for example multiple tabs), each of those will have a seperate history tracked in .bash_sessions. If you reboot your Mac and the terminal windows are restored, you'll find that each still have their own history - and only their own history.



When you close down a bash session, Apple's system will merge the history for that specific session into the global .bash_history file. Then when you open a new terminal (and thus bash session), it will start with that merged history containing history from potentially multiple sessions.



This is all handled by the /etc/bashrc_Apple_Terminal script.



Now that you know how it works, here are some possible causes for what you're seeing:



  • You may accidentially have removed the history yourself (history -c)


  • Your Mac could be infected with malware and/or hacked, and someone else is removing your .bash_history file


  • You have software installed that periodically empties/removes .bash_history


These reasons are not that likely, I would say.



Now there's one last possible cause:



There's a known race-condition in handling the bash histories. If you close down multiple bash sessions at once (for example closing down a terminal window with multiple tabs), you might loose part of or the whole history.



This happens if the computer is "slow" while reading/writing parts of the history. Basically how it works is that your currently history is read, the file is deleted/moved away, and a new file is created, where all the history lines are written to. If this process is running multiple times at the same time, you might see that one process removes the old history, the other process read an empty history, then the first process writes out the whole history again, and then the other process deletes that and writes out a very short history containing only few recent lines - as it didn't read anything in. This bug shows up as exactly what you have described.



The fix is simply to close one bash session at a time to let the system have time to write out everything correctly.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 25 at 13:14









jksoegaardjksoegaard

20k2150




20k2150












  • Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

    – Dark Star1
    Mar 25 at 14:18











  • Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

    – QuickishFM
    Mar 25 at 14:31











  • This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

    – Dark Star1
    Mar 25 at 15:16











  • As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

    – jpa
    Mar 25 at 19:18











  • The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

    – jksoegaard
    Mar 25 at 19:42

















  • Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

    – Dark Star1
    Mar 25 at 14:18











  • Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

    – QuickishFM
    Mar 25 at 14:31











  • This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

    – Dark Star1
    Mar 25 at 15:16











  • As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

    – jpa
    Mar 25 at 19:18











  • The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

    – jksoegaard
    Mar 25 at 19:42
















Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

– Dark Star1
Mar 25 at 14:18





Thanks for your explanation I will see if I can replicate this given your answer and get back to you. I am aware that it may not necessarily happen on the first try, but I'd like to be sure it is replicable.

– Dark Star1
Mar 25 at 14:18













Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

– QuickishFM
Mar 25 at 14:31





Also just want to add to the malware part - a common OS X RAT known as Eggshell has a macOS payload that actually executes history -wc as part of its code after the main payload, such that all traces of the payload injection command are wiped. Not saying its necessary Eggshell but it could be something common if someone wanted to hide their traces...

– QuickishFM
Mar 25 at 14:31













This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

– Dark Star1
Mar 25 at 15:16





This has only happened to me twice and I doubt it is that malware but thanks for the info. Ill look out for it just in case

– Dark Star1
Mar 25 at 15:16













As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

– jpa
Mar 25 at 19:18





As a workaround, I have this in my bashrc: export PROMPT_COMMAND='echo $(date +%Y-%m-%dT%H:%M:%S) $(pwd): "$(history 1 | head -c 512 | sed "s/^[ ]*[0-9]+[ ]*//" )" >> ~/.bash_history_full; echo -ne "33]0;$PWD##*/07"' which will store each command after it is executed.

– jpa
Mar 25 at 19:18













The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

– jksoegaard
Mar 25 at 19:42





The disadvantage there is thought that it won't seperate sessions for you - so it will be hard to make sense of stuff afterwards if you have many sessions (for example some local and some remote).

– jksoegaard
Mar 25 at 19:42

















draft saved

draft discarded
















































Thanks for contributing an answer to Ask Different!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f354746%2fwhy-is-bash-history-periodically-wiped%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

Tähtien Talli Jäsenet | Lähteet | NavigointivalikkoSuomen Hippos – Tähtien Talli

Do these cracks on my tires look bad? The Next CEO of Stack OverflowDry rot tire should I replace?Having to replace tiresFishtailed so easily? Bad tires? ABS?Filling the tires with something other than air, to avoid puncture hassles?Used Michelin tires safe to install?Do these tyre cracks necessitate replacement?Rumbling noise: tires or mechanicalIs it possible to fix noisy feathered tires?Are bad winter tires still better than summer tires in winter?Torque converter failure - Related to replacing only 2 tires?Why use snow tires on all 4 wheels on 2-wheel-drive cars?