RCP Failure - whilst copying

[AnotherAlan]

Morning all,

I have a wierd one. My stone-age DBA's are still using rcp to copy between systems (even though they have been told to use scp), this morning they reported that an rcp command started working and then failed half way through with permission denied errors. I have checked .rhosts and all is ok with that. I added an additional entry to use the fqdn into the .rhosts file and they restarted. This time the copy moved further than the previous attempt but then fell over again.
I have checked all permissions and uid's on both servers and all looks good.
Anyone have any other pointers or clues.

Thanks
Alan

 

[djr111]

how about the /etc/hosts.equiv. I believe permissions for rshd services can also be set there.

also

The 'rcp' command (or similar commands like 'rsh') also runs '$home/.cshrc', and, 'rcp' fails if there interactive commands (like 'stty') in this file - such commands should be removed before running 'rcp'. Or use conditionals such as: ' if ($USER == 0 || $?prompt == 0) exit '. There is actually a '.cshrc' RESTRICTION in the 'man pages' for 'rcp', ie.:


are you using nis?

 

[maximusGeek]

Its hard to get people to stop using RCP... so I just turned if off and sent out an email with SCP syntax. Problem solved

 

[sbrews]

bjensen210 - I tried that once. The stone-agers complained to management that they couldnt do their job without rcp - even though I gave the explicit step by step directions for scp. Long story short... I had to turn rcp back on... I no longer work there (my choice).

 

[maximusGeek]

sbrews - I used the excuse that company policy has been mandated and before that... my customer policy mandated removal of RCP and for the sake of CM policy, we must maintain our configuration baseline. I didn't have to but ISO 9000 CMMI level..... could have all come out if I needed to argue with the suits.

 

[AnotherAlan]

Thanks for the input djr111. I'll look into your ideas.

We have implemented ssh and consequently scp across the cam pus, unfortunately our overworked DBA's (!!!) haven't had the time to rewrite their copy scripts yet...despite my giving them a one line sed statement.

Thanks to all.
Alan