I rebooted a VM running Atomic and lost bash history, but I was unaware that reboots were supposed to *preserve* bash history! I thought that was expected behavior - a violent end to a process wouldn't necessarily allow its buffers to be flushed.
On Mon, Nov 24, 2014 at 11:36 PM, Kushal Das <kushaldas@xxxxxxxxx> wrote:
On Sun, Nov 23, 2014 at 8:32 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote:
>
> The other day during the Atomic Test Day jzb and I noticed that we
> were losing bash history (seemingly randomly). Today I dug into it a
> bit more. If you reboot a machine from a bash session then you will
> lose all of your history for that session. Note the following is from
> the F21 Cloud image:
>
> [root@f21 ~]# cat .bash_history | wc -l
> 2
> [root@f21 ~]# history | wc -l
> 123
> [root@f21 ~]# reboot
> Connection to 172.24.4.228 closed by remote host.
> Connection to 172.24.4.228 closed.
> [root@localhost ~(keystone_admin)]#
> [root@localhost ~(keystone_admin)]# ssh -i key1.pem
> fedora@172.24.4.228
> Last login: Thu Nov 20 18:54:48 2014 from 172.24.4.225
> [fedora@f21 ~]$
> [fedora@f21 ~]$ sudo su -
> [root@f21 ~]# history | wc -l
> 3
>
> Has anyone else seen this? Is there an existing bug report?
>
I can not reproduce this in a few images I tried.
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
--
Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick http://j.mp/CompJournoStickOverview
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday.
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
