01-17-2005
Looks like the problem is resolved regarding the ufsdump issue. It was explained to me using very techie jargon, but the network admin that I spoke to made a few changes to a "policy setting", checked that rsh from apples worked ok, and pronounced it "fixed". He told me to run the ufsdump (which is now working) and let him know in the morning if the logs show successful dumps.
This should close the thread out, but I'm left wondering "What would cause the rsh to stop working after the patch?" I'll have to look further into the patch docs to see if rsh is affected.
Thanks RTM for the help. I know more about /etc/hosts.equiv and /.rhosts to know that those two files were correctly populated with the apple host name on oranges to know that it should have worked.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to ftp to my linux box from windows and from unix and its not working. I can telnet just fine, but ftp doesn't work. Where should I start looking? What config file is it that controls the ftp? Why does telnet work and ftp not? I'm using redhat 6.1, samba's working for browsing the... (33 Replies)
Discussion started by: kymberm
33 Replies
2. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
3. UNIX for Dummies Questions & Answers
Hello Everybody:
I want to make a patch that telnet me directly to a specific IP with the specidied username and password.
I tried the following :
------------------------------------------
telnet 10.11.161.10
user
pass
----------------------------------------------------
but didnt log... (2 Replies)
Discussion started by: aladdin
2 Replies
4. UNIX for Dummies Questions & Answers
telnet at my system is behaving stange. Some times I am able to telnet to other machines but sometimes it stop doing that. Then i have to reboot the machine and most of the time (not 100%) it works. SImilar is the case with SSH. Sometime it works , some time it don't. i am new to Unix and I do not... (1 Reply)
Discussion started by: deepak_pathania
1 Replies
5. Shell Programming and Scripting
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies
6. Solaris
Hello,
The 10_Recommended update failed on 3 of 191, which was patch 119254-73 (the 1st 2 patches were skipped). I looked up the patch on Sunsolve (http://sunsolve.sun.com/search/document.do?assetkey=1-21-119254), which stated that 121133-02 was a required patch for 119254-73. I did a "showrev... (7 Replies)
Discussion started by: stringman
7 Replies
7. Windows & DOS: Issues & Discussions
I am trying the below ANT telnet task:
<telnet userid="appldev" password="techm123" server="${BT_Server}">
<read>/u01/appldev/devappl/po/11.5.0/reports</read>
<!--write>cd /u01/appldev/devappl/po/11.5.0/reports/</write-->
<write>ls</write>
<read... (0 Replies)
Discussion started by: Dip
0 Replies
8. Solaris
hi Everyone
telnet and ssh not working in Solaris 8 .... but it pinging.... i also checked
/etc/services
/etc/inet/inetd.conf
ps -ef | grep telnet
ans default router ... everythinking is ok .... when i connect telnet then suddently closed ... and ssh is connection refused ...
help... (1 Reply)
Discussion started by: coolboys
1 Replies
9. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
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