We have a service that we start up remotely with rsh but unfortunately, the rsh never returns to the calling server. This seems to be because the processes of the service we've just started hold the port open.
When run locally on the command line, all is well with the simple script and I can log off the session without issue or other prompt. When called with rsh, the script called does complete (we have logging to show that), so I'm wondering how I can disinherit/detach the service processes started up.
Server where script will run is AIX 5.1 and the server calling is RHEL 6.3
Suggestions would be most welcome. Many thanks, in advance,
Robin
Liverpool/Blackburn
UK
---------- Post updated at 11:59 AM ---------- Previous update was at 11:21 AM ----------
Cancel that. I managed it with a nohup xxxxx & call to start the service inside the script.
Hi All,
My rsh connecion is very slow, what should I look for...???
Note : I get the rsh connection, but it takes time.
Thanks & Regards,
jumadhiya. (3 Replies)
Hi
Can someone help me what is the problem, when i try to login via ftp, though i entered the correct password, i got an error message
Connection refused.
please help. thanks (3 Replies)
I am trying to connect to a remote server using rsh.
first i have given the following command.
$ rsh 242.13.45.54 -l
now i got the following message
"connect to address 242.13.45.54: Connection refused
Trying krb4 rlogin...
connect to address 242.13.45.54: Connection refused
trying... (1 Reply)
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Hi,
I have logged into a system using Telnet and iam unable to close the connection to connect to the next system using arrays.
Iam getting error "Connection Timed Out"
Iam using net::Telnet module.
Please suggest.. (1 Reply)
Hi. !
When I use the 'NOHUP' along with the '&', the process will be running in the background. Even when I attempt to close (Meaning 'EXIT') the session (say PUTTY in this case), it wont exit unless the process is completed.
But, say when I forcefully terminate the session (SHUT DOWN the... (2 Replies)
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
Can ssh to server. Asks for password.
Then seems to time out and close the connection. Any ideas?
---------- Post updated at 09:30 AM ---------- Previous update was at 07:51 AM ----------
Here is output from ssh -vvv -l user <IPaddress>
debug3: packet_send2: adding 64 (len 59 padlen 5... (4 Replies)
I'm trying to remotely run an upgrade script (via SSH) that update the SSH script on several hosts, just need to add several flags for the ssh command to look like this:
ssh -Nf -i id_logs -o ExitOnForwardFailure=yes -o StrictHostKeyChecking=no -o ServerAliveInterval=60 -o ServerAliveCountMax=5... (4 Replies)
Hello,
I am running a bash script to do an rsync back on a computer running MacOS High Sierra. This is the script I am using,
#!/bin/bash
# main backup location, trailing slash included
backup_loc="/Volumes/Archive_Volume/00_macos_backup/"
# generic backup function
function backup {... (12 Replies)
Discussion started by: LMHmedchem
12 Replies
LEARN ABOUT OSX
rsh
RSH(1) BSD General Commands Manual RSH(1)NAME
rsh -- remote shell
SYNOPSIS
rsh [-46dn] [-l username] [-t timeout] host [command]
DESCRIPTION
The rsh utility executes command on host.
The rsh utility copies its standard input to the remote command, the standard output of the remote command to its standard output, and the
standard error of the remote command to its standard error. Interrupt, quit and terminate signals are propagated to the remote command; rsh
normally terminates when the remote command does. The options are as follows:
-4 Use IPv4 addresses only.
-6 Use IPv6 addresses only.
-d Turn on socket debugging (using setsockopt(2)) on the TCP sockets used for communication with the remote host.
-l username
Allow the remote username to be specified. By default, the remote username is the same as the local username. Authorization is deter-
mined as in rlogin(1).
-n Redirect input from the special device /dev/null (see the BUGS section of this manual page).
-t timeout
Allow a timeout to be specified (in seconds). If no data is sent or received in this time, rsh will exit.
If no command is specified, you will be logged in on the remote host using rlogin(1).
Shell metacharacters which are not quoted are interpreted on local machine, while quoted metacharacters are interpreted on the remote
machine. For example, the command
rsh otherhost cat remotefile >> localfile
appends the remote file remotefile to the local file localfile, while
rsh otherhost cat remotefile ">>" other_remotefile
appends remotefile to other_remotefile.
FILES
/etc/hosts
/etc/auth.conf
SEE ALSO rlogin(1), setsockopt(2), rcmd(3), ruserok(3), auth.conf(5), hosts(5), hosts.equiv(5), rlogind(8), rshd(8)HISTORY
The rsh command appeared in 4.2BSD.
BUGS
If you are using csh(1) and put a rsh in the background without redirecting its input away from the terminal, it will block even if no reads
are posted by the remote command. If no input is desired you should redirect the input of rsh to /dev/null using the -n option.
You cannot run an interactive command (like ee(1) or vi(1)) using rsh; use rlogin(1) instead.
Stop signals stop the local rsh process only; this is arguably wrong, but currently hard to fix for reasons too complicated to explain here.
BSD October 16, 2002 BSD
02-17-2014
and the server calling is RHEL 6.3