Bug 1199026 - Current bash history not saved when the system is rebooted
Summary: Current bash history not saved when the system is rebooted
Keywords:
Status: CLOSED DUPLICATE of bug 1170765
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 10:39 UTC by Sitsofe Wheeler
Modified: 2015-03-05 13:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:20:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sitsofe Wheeler 2015-03-05 10:39:15 UTC
Description of problem:
The current bash history isn't saved when the system is rebooted.

Version-Release number of selected component (if applicable):
systemd-216-20.fc21.x86_64
bash-4.3.33-1.fc21.x86_64

How reproducible:
Reproducible every time.

Steps to Reproduce:
1. Log in at a VT as root.
2. Type the following
# Will this make it into the bash history
reboot
2. After the machine has rebooted type log in at a VT as root.
3. Type
history | grep "[W]ill this make it into the bash history"

Actual results:
No results are printed.

Expected results:
A line like
  250  # Will this make it into the bash history

Additional info:
This issue can also be reproduced by exchange the root VT for a root ssh connection. This issue is not present on Ubuntu 14.04 (upstart 1.12.1-0ubuntu4, bash 4.3-6ubuntu1) or Fedora 20 (systemd-208-29.fc20.x86_64, bash-4.2.53-2.fc20.x86_64)

Comment 1 Jan Synacek 2015-03-05 13:20:21 UTC

*** This bug has been marked as a duplicate of bug 1170765 ***


Note You need to log in before you can comment on or make changes to this bug.