Session recording

[Kenny Lussier]

On Fri, Mar 28, 2008 at 11:19 PM, Ben Scott <dragonhawk at gmail.com> wrote:
> On Fri, Mar 28, 2008 at 9:48 PM, Kenny Lussier <klussier at gmail.com> wrote:
>  > Using script isn't an option because it logs all of the control characters ...
>
>   Why not just filter out the control characters after the fact, with
>  Perl or sed or whatever?  I've done something like that in the past.
>  The script command would seem to be exactly what you're asking for --
>  "record terminal sessions on Linux systems".  Any terminal session is
>  going to include control characters, pretty much always, so you'll
>  have to filter them somehow.

The control characters aren't the only reason that script doesn't work
for us. Script will write out to a file, but the lines aren't time
stamped, so it's impossible to know when a command was run. Also, the
file would need to be writable by the user, which defeats the point of
all the logging :-)

I've been looking at the bash-paranoia patch, which might fit the
bill. It writes out all commands executed to syslog, which is nice. It
doesn't record the output, though. The other problem is scripts.
Someone can copy a script to a box and run it, and the only thing that
is logged is the executed script name, not what was actually done...

So many holes, so little time.

Thanks,
Kenny