Is there a way that I can remotely control a user's ssh session so I can see what they are doing and walk them through the problem they are having on my AIX based application?
The following is far from being a fullblown solution and you can't control another session (that is: enter commands on the users behalf), but it is built-in and readily available: the wall command. You can use it (as root) to make a message appear in very users session.
The format is:
Whatever is enclosed in the single quotes goes to every terminal.
You can also explore the talk command, which you can use to have double-sided conversations with one user at a time.
mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why?
AHHHH!!
I have been connecting to the server with the line: ssh userid@website.com
The remote server accepts my password; logs me in with ssh; posts a lovely welcome message AND closes the session. Is this a "term... (0 Replies)
Dear All ,
I want to Access my office computer form the home.
The enviourment is like the following :
1- From my home I connect for the office via VPN connection to Unix server lets say it's IP is 11.11.11.11 and till now every thing is OK and I can access the machine normally .
2- In my... (3 Replies)
Hi,
Not sure if this is possible, I have a server (SERVER1) that is currently set up as a remote SSH host. My client SSH host (SERVER2) is connecting to SERVER1 to scp a file with no password.
I now have a need to set up a third server (SERVER3) as a remote SSH host and I need SERVER1 as a... (4 Replies)
I am using Net::SSH::Expect to connect to the device(iLO) with SSH. After the $ssh->login() I'm able to view the prompt, but not able to send any coommands.
With the putty I can connect to the device and execute the commands without any issues.
Here is the sample script
my $ssh =... (0 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
I am pretty new to linux so forgive me for asking a basic question :P
I am using SSH to control 40 machines. What i am trying to do is remotely bash a shell script on each machine. I am using a for loop to bash every script, code as follows.
code in host machine runallworkers.sh:
...
... (2 Replies)
Hi Folks,
I want to create VNC session on the Remote RHEL machine on which ssh access is denied. Is there any way so that I can create VNC session without ssh access. Let me know all possible ways! (1 Reply)
Hi everyone, after about 2 days of scratching my head on this one, I'm finally ready to punt this and ask for some actual help. Here's the situation. We have 1 server, that runs multiple VM's. To gain access to those VM's we ssh from host01 to the other vm hosts. For example when we first log... (4 Replies)
Hello,
I am trying to login to multiple servers and i have to run multiple loops to gather some details..Could you please help me out.
I am specifically facing issues while running for loops.
I have to run multiple for loops in else condition. but the below code is giving errors in for... (2 Replies)
Discussion started by: mohit_vardhani
2 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)