Comments on: Logging bash history to syslog using traps http://backdrift.org/logging-bash-history-to-syslog-using-traps Thu, 17 May 2012 15:38:12 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: David Douthitt http://backdrift.org/logging-bash-history-to-syslog-using-traps/comment-page-1#comment-929 David Douthitt Wed, 18 May 2011 19:57:12 +0000 http://backdrift.org/?p=234#comment-929 Job control should not be affected - at least, I don't know why it would be. The function log2syslog doesn't actually execute the command, but rather sends a copy of the last history output to syslog. Where this would fail is if the DEBUG trap is ever skipped - or skippable. Also, if the trap can be changed by the user, then this function can be removed. The ideal way is to modify the source code or to enable the log to syslog capabilities of Bash 4.1. http://wiki.bash-hackers.org/bash4 Job control should not be affected – at least, I don’t know why it would be. The function log2syslog doesn’t actually execute the command, but rather sends a copy of the last history output to syslog.

Where this would fail is if the DEBUG trap is ever skipped – or skippable. Also, if the trap can be changed by the user, then this function can be removed.

The ideal way is to modify the source code or to enable the log to syslog capabilities of Bash 4.1.

http://wiki.bash-hackers.org/bash4

]]> By: Paul Reiber http://backdrift.org/logging-bash-history-to-syslog-using-traps/comment-page-1#comment-433 Paul Reiber Fri, 05 Nov 2010 06:10:40 +0000 http://backdrift.org/?p=234#comment-433 If you're used to using ^Z, bg, fg, etc. you'll find this cumbersome, as those stop working. If you’re used to using ^Z, bg, fg, etc. you’ll find this cumbersome, as those stop working.

]]> By: Timo Juhani Lindfors http://backdrift.org/logging-bash-history-to-syslog-using-traps/comment-page-1#comment-350 Timo Juhani Lindfors Mon, 14 Jun 2010 09:36:52 +0000 http://backdrift.org/?p=234#comment-350 If you just hit enter multiple times the log claims that you actually executed the command multiple times too. Any suggestions on how to improve this? If you just hit enter multiple times the log claims that you actually executed the command multiple times too. Any suggestions on how to improve this?

]]>