From: DLStewart (dlstewart@xxxxxxxxxxx)
Date: Wed Jun 14 2000 - 15:26:03 GMT-3
OK. That's a big problem on a lot of topics, we learn what
works without knowing the underlying concepts.
The "exec" is short for executive. It is a process that runs
the CLI (command line interface). With an exec, a tty default,
connecting to the tty (a normal tia-232 async port) with a
terminal will let the user hit enter and get a response from
the terminal server. This can be a prompt for a password or
the CLI prompt, of course.
The problem we are talking about happens when you connect a tty
line (which has an exec process running) to a console port of
a router (which has an exec process running).
When you connect an exec to an exec, you can get chatting. This
happens when one of the execs sends characters (usually with a
carriage return at the end) to the other. The other exec responds
with HUH? (with a carriage return at the end). The first exec
says HUH? back (one HUH? per carriage return it sees). This is
why there is an indication of "incoming connection" when the port
is hung. A "cle line" will usually stop it, but may not if the
other exec isn't finished with the queue full of messages it
has to respond to.
(I know this is more detail than necessary, but this is a list
with all levels of users. Please don't feel I am over explaining
to you just because you asked the question.)
Dave
- - - - -
At 09:43 AM 6/14/00, Roger Wang wrote:
>Dave,
>
>Could you explain a little bit more about the "no exec" command under tty?
>I use it myself and it works, but I can't seem to figure out why it's
>needed.
>
>Thanks,
>
>Rog
...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:42 GMT-3