cancel
Showing results for 
Search instead for 
Did you mean: 

HPUX QA

 
SOLVED
Go to solution
Highlighted
Frequent Advisor

HPUX QA

1>What is similar file to .rhosts in HPUX
I can find this file by using
#find / -name .rhosts
How to configure .rhosts in HPUX
"Success is matter of law not luck, Make ur own & follow them -Shivkhera[You Can Win] "
19 REPLIES 19
Highlighted
Honored Contributor
Solution

Re: HPUX QA

Hey

it is also .rhosts in the home directory of a user.

check:
man .rhosts
man rlogin

content of .rhosts
servername username

Regards
Highlighted
Honored Contributor

Re: HPUX QA

hi,

.rhosts is not there by default, you need to create one in / directory.

WK
Problem never ends, you must know how to fix it
Highlighted
Frequent Advisor

Re: HPUX QA

How to configure rsh or remsh in HPUX ????????????
"Success is matter of law not luck, Make ur own & follow them -Shivkhera[You Can Win] "
Highlighted
Honored Contributor

Re: HPUX QA

See the documentation - http://docs.hp.com/en/B2355-90827/ch06s01.html

regards,
ivan
Highlighted
Honored Contributor

Re: HPUX QA

On ServerA
$cat /home/user1/.rhosts
ServerB user1

On ServerB
$cat /home/user1/.rhosts
ServerA user1

Test it on ServerA as user1
$remsh ServerB hostname
ServerB

don't forget to assign points!
Highlighted
Frequent Advisor

Re: HPUX QA

jadeja is HPUX m/c sfqaopt is linux m/c

I have configured but rsh not working but remsh is working ............giving sfqaopt23 not found
[root@jadeja][/]rsh sfqaopt23 ls
rsh: sfqaopt23: not found.
[root@jadeja][/]remsh sfqaopt23 ls
showing list of files
abc
pqr
xyz
[root@jadeja][/]
"Success is matter of law not luck, Make ur own & follow them -Shivkhera[You Can Win] "
Highlighted
Honored Contributor

Re: HPUX QA

Have you configure your DNS correctly on your linux server? or you can also configure /etc/hosts

check with
$nslookup sfqaopt23
Highlighted
Honored Contributor

Re: HPUX QA

man remsh

rsh is used in HPUX as restricted shell.
Highlighted
Honored Contributor

Re: HPUX QA

> #find / -name .rhosts

Not a good idea at all, especially on big machines. find / might take serveral hours to complete and severely load the server needlessly. The .rhosts file only works if it is in the $HOME directory so limit the search to the $HOME directories and since it MUST reside in the user's $HOME directory, don't use find, just use ll:

ll /home/*/.rhosts

But as mentioned, .rhosts never exists by default as it can be a severe security risk. You create the file in the user's $HOME. Do this as root by:

echo "remote-host username" >> /home/username/.rhosts
echo "remote-IPaddr username" >> /home/username/.rhosts

where remote-host is the hostname of the remote computer and the username is the user that will be accesssing this local computer. Because there are so many wrong ways to setup hostname resolution, always put the IP address in the .rhosts file. Then change the permissions and ownership:

chown localUserName /home/localUserName/.rhosts
chmod 600 /home/localUserName/.rhosts

Then test with a simple command from the remote system:

(On HP-UX)
remsh localHostname pwd

(On other Unix systems)
rsh localHostname pwd


Bill Hassell, sysadmin