Try holding ctrl or alt while left/right/middle(both button) clicking on
the xterm window.
Henry
E. Marquez <e...@u.washington.edu> wrote in article
<Pine.A41.3.96a.98051...@dante26.u.washington.edu>...
> Hi,
> I need to find out how to create a log of a telnet session in my xterm.
> It's prob. something simple but I don't see it. I need to be able to
> record my telnet session with my Linux server. I'm using RedHat 5.0 if
> that helps at all. Please help!
> Thanks.
>
>
> Eric B. Marquez
> e...@u.washington.edu
>
>
>
Try the `script` command. It spawns a shell and logs whatever is on your
screen until you exit. It's neither telnet nor xterm specific.
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading
a simpler solution: use 'script' (unless you've got logging enabled - that's
on the ctrl/left mouse button, "Log to File").
: Try holding ctrl or alt while left/right/middle(both button) clicking on
: the xterm window.
: Henry
: E. Marquez <e...@u.washington.edu> wrote in article
: <Pine.A41.3.96a.98051...@dante26.u.washington.edu>...
:> Hi,
:> I need to find out how to create a log of a telnet session in my xterm.
:> It's prob. something simple but I don't see it. I need to be able to
:> record my telnet session with my Linux server. I'm using RedHat 5.0 if
:> that helps at all. Please help!
:> Thanks.
:>
:>
:> Eric B. Marquez
:> e...@u.washington.edu
:>
:>
:>
--
Thomas E. Dickey
dic...@clark.net
http://www.clark.net/pub/dickey
http://www.columbia.edu/kermit/ck60.html
as your telnet client, instead of regular Telnet. Give it a LOG SESSION
session command. Sessions are recorded by default in "text" mode, meaning
that CRLFs become LFs and NULs are stripped, but you can also request
binary mode (every incoming byte is recorded).
- Frank
Mind a naive question?
Why not just use tee?
--
Carl Fink ca...@dm.net
Manager, Dueling Modems Computer Forum
<http://dm.net>
YES YES YES! THIS GUY HAS A FIRM GRASP OF THE OBVIOUS!
Wake up guys! You should have thought of this yourselves!
Of the obvious, but not the useful.
>Wake up guys! You should have thought of this yourselves!
Urm. Nope. If all you *ever* do in your shell is operations that don't
require a screen mode, then it's probably fine...
But if you *do* do screen mode things, tee breaks them, and breaks them
horribly.
'script' doesn't break screen mode things, and nor does turning on XTerm
logging.
Later,
David
--
| da...@unico.com.au (David Goh, Unico Computer Systems, +61-3-9866-5688)
I have a theory that it's impossible to prove anything,
but I can't prove it.
>Urm. Nope. If all you *ever* do in your shell is operations that don't
>require a screen mode, then it's probably fine...
>
>But if you *do* do screen mode things, tee breaks them, and breaks them
>horribly.
Do you routinely change screen modes in telnet? I never have. I've
been using various telnets for . . . about ten years, I guess.
--
Carl Fink ca...@dm.net
Maybe you should get a Sherlock Holmes outfit to disguise the fact that
you have no clue. --Scott Adams
I don't change screen modes (I'm assuming you mean changing the rows and
column settings, or messing with TERMCAP, etc) in telnet usually, but I
certainly use vi, nethack, mutt, elm, and a whole bunch of other curses
or slang based programs over telnet.
If you pipe any of them through tee, they'll break, and break horribly.
Now, while I'm perfectly capable of using vi in ex mode, or ex itself in
line mode, and I have certainly done so under conditions of horrible
lack of bandwidth or horrible net lag to avoid the curses overhead, I
don't *like* it, and see no reason to operate that way.
Are you saying that you have never used *any* curses based programs
across telnet in ten years? I've done so ever since seven years ago,
which is when I started doing unix computing things.
Later,
David
--
| da...@unico.com.au (David Goh, Unico Computer Systems, +61-3-9866-5688)
"Heisenberg may have slept here"