Score:1

Server

Saving the date to actual bash history file

OB7DEV

11/17/22, 11:36 PM

When adding "HISTTIMEFORMAT" to bashrc, the timestamps of when a command was executed are made available when running the "history" command.

But the timestamps themselves are not saved to the bash_history file (atleast not in plain text).

I am looking for a solution that will write the timestamp to the file itself so that archived .bash_history files from various workstations can be viewed in an editor outside the userspace and still contain the timestamps of when commands were executed.

If the timestamps are being saved to the history file itself but just not viewable in an editor when opening the bash_history file, and it is still possible to view these timestamps by using the history command itself on a rogue bash history file, then that would also suffice.

Thanks

283

3 + 2

bashrc

glenn jackman

11/18/22, 2:44 AM

Just adding the variable to the bashrc is not enough: you need to source the bashrc in each of your open shells to "activate" the variable.

glenn jackman

11/18/22, 2:47 AM

And the history file is only written/appended when a shell exits.

Score:1

Server

EchoMike444

11/18/22, 12:13 AM

This is a example of bash history ( when using HISTTIMEFORMAT )

#1625963751
sleep 45 ; ssh proxy.lan

the number 1625963751 is the unix timestamp ( https://en.wikipedia.org/wiki/Unix_time ) .

if you are using linux , date has a option to display this date in human form .

em444$ date -d @1625963751
Sat Jul 10 20:35:51 EDT 2021

0 + 2

OB7DEV

11/18/22, 12:31 AM

How do I append the unix timestamp to each command in a bash file? When opening old bash historys I have, there is no #number above each command as there is in your example. Opening a bash_history file in vim just gives a list of commands. Each line is a command, there's no time stamps above each line.

EchoMike444

11/18/22, 12:38 AM

if you dont use HISTTIMEFORMAT , you will not have timestamp .

Score:0

Server

George Y

11/18/22, 3:34 AM

edit /etc/bashrc and add this line to the bottom:

PROMPT_COMMAND="echo `date +'%F %H:%M'` `whoami` `history|tail -1` >> ~/history.txt; $PROMPT_COMMAND"

I am not sure if you change ~ to root, \root\history.txt can be accessible to all users yet.

0 + 4

Gerard H. Pille

11/18/22, 3:37 AM

\root\history.txt ???

George Y

11/18/22, 4:02 AM

`~/history.txt` means the file `history.txt` in current user's home directory. `/root/history.txt` means the file in root directory. I assume you want to save historical commands to a specific file if you want a timestamp on each commands.

Gerard H. Pille

11/18/22, 6:06 AM

It's only that backslashes have a different meaning on unix. Apart from that, 'history -1' may be cheaper than piping through tail.

OB7DEV

11/19/22, 9:35 PM

It seems I cannot get the history|tail -1 output appended to history.txt. The rest of the command works though. So my history.txt has date, user, but no command...

Score:0

Server

George Y

11/21/22, 7:22 AM

export HISTTIMEFORMAT='(%Y-%m-%d) (%H:%M:%S) ' Try this line.

0 + 0

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Saving the date to actual bash history file

TH: บันทึกวันที่ไปยังไฟล์ประวัติการทุบตีจริง

RO: Salvarea datei în fișierul istoric bash real

RU: Сохранение даты в фактическом файле истории bash

VI: Lưu ngày vào tệp lịch sử bash thực tế

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.