Matt Murphy on 4 Sep 2011 05:47:40 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] Capturing command line, and stdio and error with bash

Have you looked into using an advanced keylogger?  I mean, this sounds
like a problem some "black hat" solved 15 years ago...  Mind you, I
have no idea where to find such thing, but you're definitely
reinventing an extant wheel.


On Sun, Sep 4, 2011 at 8:35 AM, Edmond Rodriguez
<> wrote:
> Well there has been lots of mail about redirection in bash.
> I have a question about logging.
> The script command logs ALL output to the terminal (editing keys,
> backspaces, up arrows, ...). Â I just want what I see after I hit the
> enter key.
> If I type "datx <backspace> e", Â I want to see "date" in my script
> file, not "datx <backspace> e", and I don't want to have to make my
> display reinterpret the editing commands either, so I can see it right
> (generally messes everything up because of cursor movement escape
> sequences often used).
> But how does one get a hybrid between what the history logging does
> and what script does?
> So I would want a script that has only the final result of my command
> entered (like history does) I entered, not the editing keystrokes as
> well (back space, emacs or vi control keys....cursor movements), and
> of course whatever else gets output to the terminal. Â ÂI realize if a
> formatting strings goes to the terminal from an *application* I am
> running, ÂI will get that, but I am just thinking of general basic
> text i/o going to the terminal from an application.
> Edmond
> ___________________________________________________________________________
> Philadelphia Linux Users Group     --    Â
> Announcements -
> General Discussion Â-- Â
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --