On Tue, 13 Apr 2010, Aleksey Tsalolikhin wrote: > I understand. Have you checked this user's shell command history? > > You might want to set this variable in your users' bash shell: > > HISTTIMEFORMAT > > If this variable is set and not null, its value is used > as a format string for strftime(3) to print the time stamp associated > with each history entry displayed by the history builtin. If this > vari- > able is set, time stamps are written to the history file > so they may be preserved across shell sessions. > > This will tell you when command was run. Caveat: once you set this > variable, and run "history", you'll see timestamps next to commands -- > but ignore the commands PRIOR to setting the variable, they'll be > bogus rather than blank.
All that is already being done and the last line in the history is being logged to syslog every time the shell returns to the command prompt. This will probably be good enough, but the other sysadmin and I agree that it would be nice to have the command lines logged before running them instead of after they have finished. -- Matt It's not what I know that counts. It's what I can remember in time to use. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
