From: "Paul Gimpelj" <pgimpelj@sympatico.ca>
To: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: re: logging console input
Date: Tue, 25 May 2004 12:07:55 -0400 [thread overview]
Message-ID: <00ea01c44272$70eb72c0$3410fea9@zoom> (raw)
Yes. and no. a fork or Tee would be nice.
Someone suggested to use script.
but I would prefer to bounce around consoles and xconsoles.
and trap and journal all input.
thanks
paul
--------------------------------
John T. Williams reponds:
Am I right in saying that what you want is a key logger, which logs
all key strokes regardless of which terminal they are inputted to.
In fact a program that sits between the kernels main keyboard buffer
and user land programs, logging all input before any user land program
can remove them from the main input buffer?
On Tue, 2004-05-25 at 09:54, Paul Gimpelj wrote:
> Well,
>
> Say I am typing all day and night into console and want a record of my
input
> to review later.
> in case I forgot what i typed in hours ago.
>
> Under windows one hooks into the journaling hook vector. by writing a
> program in c.
> This gives the keyboard input so it can be recorded into a file.
>
> Is there a simple way to log the keyboard of the console, or does one need
> to write a module
> to hook the kernel.
>
> thanks.
>
>
> Ps.
> I am using ms mail 6. and wouldn't it be nice if i could just click reply
> and it would send my response
> to the linux-c........
>
> rather than ....
>
> or is there a different email browser set up for this mail list?
>
next reply other threads:[~2004-05-25 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 16:07 Paul Gimpelj [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 6:41 logging console input Venkatesharao, Lakshmesha
2004-05-25 13:54 Paul Gimpelj
2004-05-25 14:03 ` Michael Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00ea01c44272$70eb72c0$3410fea9@zoom' \
--to=pgimpelj@sympatico.ca \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).