.bash_history in F15/16 randomly truncated/incomplete/damaged

[suvayu ali]

Hi Ed,

On Tue, Mar 27, 2012 at 04:27, Ed Greshko <Ed.Greshko at greshko.com> wrote:
> On 03/27/2012 04:43 AM, suvayu ali wrote:
>> Hi Frantisek,
>>
>> On Sat, Mar 24, 2012 at 15:15, Frantisek Hanzlik <franta at hanzlici.cz> wrote:
>>> Now occurred to me that i can watch several (mainly roots) history files
>>> by incrond and start some script which log some events on it. Maybe it
>>> helps.
>> I recalled your post and did a check before I rebooted my laptop today
>> (after 7 days). I think you were correct and my claim that its a
>> ridiculous idea was wrong.
>>
>> This is what I did:
>>
>> 1. I closed all running apps except for a terminal.
>> 2. Executed these commands
>>    $ echo "1 test"
>>    $ echo "2 test"
>>    $ echo "3 test"
>>    $ sudo shutdown -P now
>> 3. On turning on the laptop again, I could not find either of the three
>>    commands with history | grep -E "echo.+test"
>>
>> In addition to $HISTFILE, I log all my history to a separate file. That
>> file _did_ have all the test and the shutdown commands. So we can
>> conclude bash was doing the right thing and systemctl is to blame.
>>
>> At the moment I am very busy, so I would urge you to file a bug report.
>> If you post the bug id back to the list, I'll try to add more comments
>> if I find anything with regards to this.
>>
>
> FWIW, I did the same test on a VM running F16.  After restarting, this was the last
> thing in my .bash_history file....
>
> echo "4 Test" ; sudo shutdown -P now
>
> So, it isn't clear to me that it is a consistent problem.  Maybe a race condition?
>

Actually now that you mention, I think that might be possible. When I
did the test I forgot I also run guake (a quake like drop down
terminal). So the history from my test could easily have been
overwritten by that. When I have the time I will try to repeat the
test in a cleaner environment (creating a new user and all that ...).

-- 
Suvayu

Open source is the future. It sets us free.