R
RowBat
Guest
What are the implications of making a symbolic link from a log... Say .bash_history to Dev/null?
OP
JasKinasis
Guest
I don't think there would be any problems with that. All data written out from bash to the .bash_history file would be redirected to /dev/null.
The only adverse effect would be that the history command would not work (as the history file is effectively empty) and you would not be able to access any previously entered commands using the arrow keys and/or the ! commands.
Personally, I find the bash history to be useful. But if you want all of your bash history to be written to the bit-bucket, that is up to you!
The only adverse effect would be that the history command would not work (as the history file is effectively empty) and you would not be able to access any previously entered commands using the arrow keys and/or the ! commands.
Personally, I find the bash history to be useful. But if you want all of your bash history to be written to the bit-bucket, that is up to you!
OP
RowBat
Guest
It was more a theory on how to dispose of logs.. I'm an infosec students...
OP
rstanley
Guest
Logs can be a valuable tool. You can always create a script to remove older backups of logs in /var/log. As for .bash_history, the permissions should already be set so that only you can see the past commands. There are better ways to control your .bash_history.
http://www.ducea.com/2006/05/15/linux-tips-take-control-of-your-bash_history/
OP
RowBat
Guest
The object was to render them useless.
OP
jesus
Guest
You can turn off history logging for the current session with: set +o history
You can clear the history with this command: history -c
Alternatively you could make an empty .bash_history file and make it inmutable.
You can clear the history with this command: history -c
Alternatively you could make an empty .bash_history file and make it inmutable.
