Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis.
Vitae congue eu consequat ac felis placerat vestibulum lectus mauris ultrices cursus sit amet dictum sit amet justo donec enim diam porttitor lacus luctus accumsan tortor posuere praesent tristique magna sit amet purus gravida quis blandit turpis.
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. porta nibh venenatis cras sed felis eget neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat in egestas erat imperdiet sed euismod nisi.
“Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque velit euismod in pellentesque massa placerat”
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget dolor cosnectur drolo.
Bash_history date
Ever try to determine what caused the latest outage by trying to determined when a command was last executed?
Look in your .bash_history (if you are running a bash shell), and you will see your recently executed commands. However, it is generally impossible to tell when the command was executed.
Part of our job includes figuring out how a problem occurred, and then implementing solutions to prevent this problem from happening again. By using HISTTIMEFORMAT with bash, we can enable timestamps in the history command, allowing for much better auditing and correlation of problems.Below is example output of the history command without HISTTIMEFORMAT:$ history | tail -3 994 ping www.mnxsolutions.com 995 ls -lart 996 grep POST access_logTo enable timestamps globally (for all users) in your history output you need the following settings:
export HISTTIMEFORMAT='%F %T 'Below is example output of the history command with HISTTIMEFORMAT:$ history | tail -3 1004 2010-07-11 13:29:29 ping www.mnxsolutions.com 1005 2010-07-11 13:29:34 ls -lart 1006 2010-07-11 13:29:38 grep POST access_logUsing bash_history with HISTTIMEFORMAT enabled makes our job easier, and will help you when trying to debug issues in the future.
Click here for additional detail or request a proposal so you can start focusing on growing your business, rather than supporting your servers.