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
Last edited by akula_1986; 10-30-2010 at 07:51 PM..
I have the following questions regrading Unix commands.
1. Could you provide the commands how to print the content of .profile and .shrc files on the screen using more and piple command? or a better way?
2. How can i use the head and tail to display lines from 25 through 75... or a better... (4 Replies)
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)
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)
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)
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)
Hi,
I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen?
Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
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
LEARN ABOUT HPUX
talk
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)