10-02-2014
I'm using CRT from VanDyke Software. I used a good old Windows Telnet session to access the HP box and ran my kill. The screen did not go blank. SO, yes, that is a terminal emulator issue with CRT. I'd be curious to know what causes this and how it can be prevented...
10 More Discussions You Might Find Interesting
1. Cybersecurity
does any one know how to kill an idle session?
I want to kill any idle sessions after 30 min... Local or remote....
i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure.....
ThAnks:rolleyes: (4 Replies)
Discussion started by: securhack
4 Replies
2. Shell Programming and Scripting
Good day. :)
I don't know exactly where or how to post this kind of stuff, but I though I'd like to have a look at my "Screen Saver" in progress. Comments welcome.
This uses bash. Just copy and pase into any file. Make o+x and run. Feel free to edit and change all u like.
Thanks.
... (0 Replies)
Discussion started by: Blooper
0 Replies
3. Programming
hi ,
Could any one tell me the command for clearing the screen in GDB session (1 Reply)
Discussion started by: useless79
1 Replies
4. Shell Programming and Scripting
Hello,
I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem.
my script is,
---
while true
do
./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt
echo "Restarting `date`"
done
---
As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies
5. Fedora
Hello sir,
Im in a Fedora 9 system.
Im using screen to invoke the session that is created by me.
Whenever we open the terminal then a session is created by the operating system. I want to know what is the name of default session in screen command.
I could not get it using "screen -ls". Can you... (3 Replies)
Discussion started by: nsharath
3 Replies
6. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
7. Shell Programming and Scripting
Hello everyone,
Following command sends word 'test' followed by an enter into a screen session (in our case screen_1). How do I print the result, if that would result ? How do I print the result, even if the program running in the session is locked ?
Thank you :)
screen -S screen_1 -X... (5 Replies)
Discussion started by: akula_1986
5 Replies
8. Shell Programming and Scripting
Im trying to make a script that prints 2 messages to a screen session, one after the other.
screen -x session44 -X stuff "`printf "Test 1\r"`"
This works fine, but adding a second lien with a different message yields no results.
Changed Subject: Please Follow Forum Rules Regarding... (1 Reply)
Discussion started by: kylecn
1 Replies
9. Shell Programming and Scripting
hi, i am on AIX 5.3. I would like to write scripts that initiate or reattach to a screen session to run some commands either from unix or Universe. Can anyone assist me with a with a wuick primer on this. I can attach or initiate a screen manually and then run the commands but I would like to... (6 Replies)
Discussion started by: dustytina
6 Replies
10. Linux
Hello friends,
I work on Linux servers via SSH (putty) and run "screen" to preserve my sessions so I can attach/detach them at anytime I wish without losing the connectivity/process disruption which is working perfectly fine.
As my team members also have root access to those servers, it is... (7 Replies)
Discussion started by: prvnrk
7 Replies
talk(1) General Commands Manual talk(1)
NAME
talk - talk to another user
SYNOPSIS
talk_party [ttyname]
DESCRIPTION
The utility is a two-way, screen-oriented communication program.
The command argument talk_party can take one the following forms:
user
where user is a login name and host is a host name.
The optional command argument, ttyname, can be used to specify the terminal to be used when contacting a user who is logged in more than
once. In absence of this argument, will try to contact the user on the user's most recently used terminal.
When first invoked, sends the following message to the party it tries to connect to (callee):
...
At this point, the recipient of the message can reply by typing:
Once communication is established, the two parties can type simultaneously, with their output displayed in separate regions of the screen.
Characters are processed as follows:
o Typing characters from LC_CTYPE classifications print or space will cause those characters to be sent to the recipient's terminal.
o Typing <control>-L will cause the sender's screen to be refreshed.
o Typing the erase, kill or kill word character will delete the last character, line or word on the sender's terminal, with the action
propagated to the recipient's terminal.
o Typing the interrupt character will terminate the local talk utility. Once the talk session has been terminated on one side, the other
side of the talk session will be notified that the session has been terminated and will be able to do nothing except exit.
o Other non-printable characters typed on the sender's terminal are converted to printable characters before they are sent to the recipi-
ent's terminal.
Permission to be a recipient of a message can be denied or granted by using the utility. However, a user may need other privileges to be
able to access other users' terminals. The utility will fail when the user lacks the appropriate privileges.
SEE ALSO
mesg(1), who(1), write(1).
STANDARDS CONFORMANCE
talk(1)