It is currently Wed, 22 May 2019 08:55:03 GMT



 
Author Message
 rsh worries shadow the Linux glamour !!

rsh troubles...

I wish there wer gurus out helping me with a minor configuration
problem that I couldn't figure out all that easily.
We need to get to a linux data transfer machine via r-tool
protocols (rsh, rcp) for remote copying files using crontab
for sceduling it.
The ftp protol has been used before (working quite fine) but
for various reasons the procedure is about to be changed to use
rcp instead of ftp.
NONE of the r-tool methods of accessing the machine work, but
just hang the prompt requiring ctrl-C to resume.
Trials show no warnings or complaints in stderr or stdout.
However note that ftp and telnet and ping DO work quite allright.
The machine is standard PC with no fancy hardware (display adapter
plus 2 * 3Com vortex cards) and kernel version 2.0.0 and with great
stability (224 days uptime).
The distribution in use is old slackware (that came with 2.0.0).
The kernel copiling options showed no aswer to problem.
Our bastard operator is breaking his nerves and the ultimate
reputation of Linux as a reliable workhorse and "as easy to
configure as any ol' UNIX" is becoming questionable by the minute
(in his reddened eyes only though).
The two machines are located in completely different networks
192...(on Linux) vs 131... (on HP).
I appreciate any hints leading to functional solution and keeping
our bulldog-like bastard from {*filter*} me in the process !
Thanks
        Olli



 Sat, 21 Oct 2000 03:00:00 GMT   
 rsh worries shadow the Linux glamour !!

  olli> rsh troubles...
  olli> I wish there wer gurus out helping me with a minor configuration
  olli> problem that I couldn't figure out all that easily.
  olli> We need to get to a linux data transfer machine via r-tool
  olli> protocols (rsh, rcp) for remote copying files using crontab
  olli> for sceduling it.
  olli> The ftp protol has been used before (working quite fine) but
  olli> for various reasons the procedure is about to be changed to use
  olli> rcp instead of ftp.
  olli> NONE of the r-tool methods of accessing the machine work, but
  olli> just hang the prompt requiring ctrl-C to resume.

The machine you're rlogging into is trying to resolve the address of
the caller back into a name.  Either put the calling machine in
/etc/hosts on the called machine, or set up DNS correctly (the called
machine must reference a usable DNS server and there must be "IN PTR"
DNS records for the caller).

  olli> Trials show no warnings or complaints in stderr or stdout.
  olli> However note that ftp and telnet and ping DO work quite allright.
  olli> The machine is standard PC with no fancy hardware (display adapter
  olli> plus 2 * 3Com vortex cards) and kernel version 2.0.0 and with great
  olli> stability (224 days uptime).
  olli> The distribution in use is old slackware (that came with 2.0.0).
  olli> The kernel copiling options showed no aswer to problem.
  olli> Our bastard operator is breaking his nerves and the ultimate
  olli> reputation of Linux as a reliable workhorse and "as easy to
  olli> configure as any ol' UNIX" is becoming questionable by the minute
  olli> (in his reddened eyes only though).
  olli> The two machines are located in completely different networks
  olli> 192...(on Linux) vs 131... (on HP).
  olli> I appreciate any hints leading to functional solution and keeping
  olli> our bulldog-like bastard from {*filter*} me in the process !
  olli> Thanks
  olli>      Olli



 Sat, 21 Oct 2000 03:00:00 GMT   
 
   [ 2 post ] 

Similar Threads

1. rsh worried about lost keyboard!

2. rexec and rsh for shadow suite

3. Worry, worry, worry... but not here.

4. NIS in linux(no shadow) with solaris (shadow)?

5. Worried about Linux Future

6. Export Restriction of Linux - A Worrying Trend.

7. Worries about Desktop Linux

8. Microsoft finiancially worried about Linux

9. Something else you won't have to worry about with Linux

10. Linux - No Worries!


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software