network profile
| bio | website | |
|---|---|---|
| location | Sunnyvale, CA | |
| age | 27 | |
| visits | member for | 3 years, 9 months |
| seen | Apr 28 at 2:23 | |
| stats | profile views | 29 |
|
Aug 12 |
comment |
Bash history loss Right, but if you ever want to reexecute a series of commands - in shell C started after A and B, or perhaps you realize you want to turn it into a script - it's been mixed. |
|
Aug 11 |
comment |
Bash history loss I understand very well how the history file is written - this is why I specified in my question that I'm using histappend. The problem is not unexpected content, but a total loss of previously stored content. |
|
Aug 11 |
comment |
Bash history loss I don't have root access on the machine this is happening on, but I'm fairly confident the drive is ok. My home directory is stored on a server in our lab (plenty of RAID, I believe) and nfs-mounted. What do you mean by "arbitrary shell history limit"? This is all happening well below HISTSIZE and HISTFILESIZE, and though I have both set large, they're well below the int bash stores them as. |
|
Aug 11 |
comment |
Bash history loss The additional benefit you cite is in many cases a downside. It's not the behavior I'm looking for, as I may be carrying out two completely separate tasks in separate shells, and do not want to intermingle their history. This would also likely not help anything. When the history disappears, it is deleting content of .bash_history - I don't expect it'd matter whether they'd been written at shell exit or by PROMPT_COMMAND. |
|
Aug 11 |
asked | Bash history loss |
|
Aug 8 |
awarded | Teacher |
|
Jul 30 |
answered | To mkdir `*/pictures` |
