RSH between Solaris 8 & 9

I am having a problem using rsh between a Solaris 8 box and a Solaris 9 box.
I can rsh from 8 to 9 and enter password etc.. and get logged in.
ie: rsh remotehost
passwd
I'm in.
The problem is I just want to pass a command (like who) from 8 to 9.
ie: rsh remotehost who
I keep getting a permission denied message.
the hosts files on remotehost does have the localhost in them?
What else am I missing.
Is the new SSH in Solaris9 causing my grief?
Thanks

I'm having the same problem. I need to rsh between Sol 9 & 7
I need to run ufsdump to remote backup library on another server.
The recently Upgraded server is sol9 needs to backup to sol7 server which has the backup library setup.
both server names are in .rhosts and /etc/hosts.equiv - that usually always works
but not now. What am I missing?
here is the cmd:
sol9> /usr/sbin/ufsdump -0uf sol7:/dev/rmt/0nc /data
This works from my other Solaris 7 servers to the sol7 server.
I do have ssh running on all the servers. I'm not sure how to run this in a ssh, I'm new to ssh.
thanks in advance
Denise

Similar Messages

Rsh between solaris

Hi: Please your help.
I have 2 solaris 8, called app01 and wss01.
Also, I have 1 script in app01, it script only contains ls -lrt command.
I try to run remotely my script from wss01, so I ran following sentence in wss01
wss01:/$> rsh app01 -l user01 script.sh
it works fine,
However when I change ls -lrt command to dtcalc (solaris calculator) in script file, so appears the message:
"can not open display"
how do I fix it?
Tks

Alternatively use SSH and run 'ssh -X remotehost dtcalc'
Some configuration of SSH on the remote host may be required - editing /etc/ssh/sshd_config to enable X tunnelling for example.
You can avoid having the password prompt by editing the authorized_keys file in the users .ssh directory
For a quick tutorial on that, check http://linuxproblem.org/art_9.html

Compiler directives to differetiate between solaris 9 and solaris 10

i have an API which makes certain function calls which are different for solaris 9 and solaris 10. i cannot add my own defines, since that would mean that applications too would have to define them.
does the Sun Workshop compiler provide any default directives to differentiate between solaris 9 and solaris 10? something like #ifdef __SunOS_5.10 or something like that?
thanks.

As explained in the C Users Guide, the compiler predefines several macros, one of which is represents the Solaris version number.
The macro name is derived from the output of the commands
uname -s and uname -r, starting with __, connected by _, and with dots replaced by _.
Running on Solaris 9:
% uname -s
SunOS
% uname -r
5.9
The defined macro name is __SunOS_5_9
On Solaris 10 you get __SunOS_5_10
__SunOS_5_9

SSH Differences between Solaris 9 and Solaris 10

I use public key authentication when connecting via SSH but have noticed a difference between Solaris 9 and Solaris 10 and wondered if it's an environment setup issue. I keep my keys in $HOME/.ssh
When connecting from Solaris 9 I can provide an identity file without a path regardless of the directory that I'm in e.g.
ssh -i my_identity_file user@hostnameThe above works even if I'm not in the $HOME/.ssh directory. But when using the same from Solaris 10 I get the following error:
Warning: Identity file my_identity_file does not exist.If I run the command from $HOME/.ssh on Solaris 10 it connects fine, and if I pass in the path like so it works fine:
ssh -i $HOME/.ssh/my_identity_file user@hostnameIs there a setting specific to SSH somewhere as I can't see anything in my environment that's different between the two systems. There's certainly no entry in $PATH that points to $HOME/.ssh. How could I get SSH to work on Solaris 10 by just providing the identity file name and not the full path
Regards
Rich

It's not explicitly defined in /etc/ssh/ssh_config, so I'm assuming it would be using the default which is ~/.ssh/id_dsa.
But surely that's irrelevant if I'm using the -i switch to provide the identity file?
Remember the problem here is that I have to provide a full path to the identity file, whereas before just the filename would do.
Rich

Networking changes between Solaris 10 x86 10/08 (u6) and previous versions?

Solaris Community:
We have a J2SE CORBA-based application (that uses the default Sun ORB) that has run without problems on Solaris 8, 9, and 10 on both SPARC and, more recently, X86 platforms. Upgrading our client side machine (X4100 M2 Opteron platform) from Solaris 10 x86 5/08 (u5) to Solaris 10 x86 10/08 (u6) has resulted in threading or socket contention issues that we have not experienced previously. Using Live Upgrade, we can quickly go back to the u5 install on the client machine .... and the problems go away .... going back to u6, however, and the problems begin to show almost immediately. Our Java code base is identical as is the version of the JDK (1.5.0_16), so it would appear that there must be an underlying change to socket, networking, or threading behavior between these two versions of Solaris.
Thus far, I've not been unable to find details of changes either in the networking support or the threading model that might explain this .... or course, I don't have great expertise in these areas.
I've tried to use 'ndd /dev/tcp SOME_PARAMETER' for all of the /dev/tcp parameters returned by 'ndd /dev/tcp \?' to try to see if there are underlying changes in the /dev/tcp parameters .... but have not found any differences between Solaris 10 u5 and u6.
Can anyone point me to resources that would discuss changes between Solaris 10 u5 or u6 that might explain the problems that we've encountered? Or, alternatively, other system parameters that I could check that might explain changes in either TCP socket or threading behavior?
Thanks for your input,
John

I have a vague memory of someone reporting something similar which turned out to be due to a solaris feature called tcp_fusion.
To check whether thats your problem or not try the following.
Add following line in the /etc/system file.
set ip:do_tcp_fusion = 0
Once the /etc/system file is updated, it will be necessary to restart the system before the workaround will take effect.

About incompatibility between Solaris 10 and Solaris 8

Dear all
I am investigating about incompatibility between Solaris 10 and Solaris 8.
But I can't find incompatibility information (I can find some compatibility imformation).
Please tell me about that if you know.
Any suggestions would be appreciated.
Thanks

Programs running on Solaris 8 should run on Solaris 10, but programs that run on Solaris 10 won't necessarily run on Solaris 8.
Solaris is always forward-compatible.
.7/M.

[Q]IPinIP setup between Solaris 8 Systems

I'd like to communicate between the two systems by applying IPinIP.
For applying IPinIP, I have configured tunnel on two systems using ifconfig command as follows:
In System A,
#ifconfig ip.tun0 plumb
#ifconfig ip.tun0 211.217.97.67 211.217.97.132 tsrc 211.217.97.67 tdst 211.217.97.75 up
#ifconfig -a
ip.tun0: flags=10028d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,UNNUMBERED,IPv4> mtu 1480 index 3
inet tunnel src 211.217.97.67 tunnel dst 211.217.97.75
inet 211.217.97.67 --> 211.217.97.132 netmask ffffff00
In system B,
#ifconfig ip.tun0 plumb
#ifconfig ip.tun0 211.217.97.75 211.217.97.132 tsrc 211.217.97.75 tdst 211.217.97.67 up
#ifconfig -a
ip.tun0: flags=10028d1<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST,UNNUMBERED,IPv4> m
tu 1480 index 3
inet tunnel src 211.217.97.75 tunnel dst 211.217.97.67
inet 211.217.97.75 --> 211.217.97.132 netmask ffffff00
Original packet that I have been testing is the ping(echo request) message.
That is packet sent from the system 211.217.97.43 to 211.217.97.132.
The result of that is described as follows:
=======
211.217.97.67 system received packet which 211.217.97.43 sent 211.217.97.132.
After appling IPinIP , 211.217.97.67 system sent that 211.217.97.75.
========
B system received packet applied IPinIP from 211.217.97.67 system.
But, 211.217.97.75 system did not forward packet to 211.217.97.132.
I could not confirmed that how 211.217.97.75 system does process that after receiving packet. What I did wrong?
I would like to know how 211.217.97.75 system does process received packet applied IPinIP.
I might expect that 211.217.97.75 system which configured tunnel forwards original packet to original destination address after IPinIP processing (decapsulation).
If you got some solutions for this problem of our system, let us know that.
And, ifconfig setting method for IPinIP setup between Solaris 8 Sytems?

agquint wrote:
What I mean was the post below your first one. But you correctly interpreted it in your next post. So "Solaris 8 containers" only works for SPARC. I don't get why Sun would only have containers support for SPARC systems. That is in total contradiction to why I would think they would develop containers in the first place: backwards compatibility to support programs that aren't yet migrated to the current version of Solaris regardless of whether they are x86 or SPARC. They have a solution but it only works at %50? hmph.There is probably just very little demand for it. During the Solaris8/Solaris9 days, Sun was killing off the x86 line. There is very little installed base of Solaris 8 x86 compared to Solaris 8 SPARC. (It wouldn't help you out, it appears, since you have SPARC binaries).
Darren

Comparison between Solaris & Windows

Can anyone help me providing info regarding the difference between solaris and windows. Are there any articles , presentations or white papers available regarding this info on net.
thanks,
Mohsin.

It's a whole other animal.

Diff between Solaris 8 and Solaris 9

Hello Experts,
Do we have a document which talks about the diff between Solaris 8 and Solaris 9
I need to know what are the new featured in Solaris 9 and etc....
Thanks in Advance.
Sunil.

Sadly, the difference between the early releases of Solaris 9 and the late releases of Solaris 8 isn't that big, since Sun backported a lot of the cool features in Solaris 9 to Solaris 8..
Hence; the answer to your question depends on which Solaris 8 and which Solaris 9 releases you are talking about.
However, a complete list of changes incoperated in the different Solaris 9 releases can be found here:
http://docs.sun.com/app/docs/doc/817-5770/6ml72d6k9?a=view
I guess there are similar lists for Solaris 10, which is even cooler than 8/9.
Enjoy!
//Magnus

Confirm Relation between Solaris 9 and SunOS 5.9

Hello,
I want to install ECC 6.0 on Oracle/Solaris.
For ECC 6.0 installation ,service.sap.com/pam mentions solaris version should be SOLARIS/SPARC 9 or SOLARIS/SPARC 10 .
On my Solaris Server, when I execute "uname -a" i get,
" SunOS 5.9 Sun4u Spac .. ".
I found following information about relation between Solaris and SunOs release,
Solaris 10 --> SunOS 5.10
Solaris 9 --> SunOS 5.9
Solaris 8 --> SunOS 5.8
Solaris 7 --> SunOS 5.7
Conclusion : So, as per above data, My OS version SunOS 5.9 corresponds to Solaris 9 which can support ECC 6.0 as per PAM.So installation is supported.
I would like to confirm above conclusion.
Please share your views.
- Nirav.

> On my Solaris Server, when I execute "uname -a" i get,
>
> " SunOS 5.9 Sun4u Spac .. ".
>
> Conclusion : So, as per above data, My OS version SunOS 5.9 corresponds to Solaris 9 which can support ECC 6.0 as per PAM.So installation is supported.
Yes.
SunOS is the "old term" for the operating system.
http://en.wikipedia.org/wiki/Solaris_(operating_system)
<...>
On September 4, 1991, Sun announced that it would replace its existing BSD-derived Unix, SunOS 4, with one based on SVR4. This was identified internally as SunOS 5, but a new marketing name was introduced at the same time: Solaris 2.[4] While SunOS 4.1.x micro releases were retroactively named Solaris 1 by Sun, the Solaris name is almost exclusively used to refer to the SVR4-derived SunOS 5.0 and later
<...>
Markus

Inetd services (telnet, rlogin ,rsh) in Solaris 9 Branded Zone

Hi,
I've got two Solaris 9 Branded Zones running on an M3000. They both use exclusive IP.
When I try and telnet, rlogin or rsh to either of my Solaris 9 zones from the other I get an error. With the r* commands I get a "Protocol error" message, and telnet just reports a terminated connection. I've tried Mr. Google, the results I get make sense for a physical host - i.e Protocol Error would occur if the server executable (in.rlogind, etc) was somehow messed up.
Just to complicate things slightly the exclusive IP NICs are on a physically separate switch from the other NICs.
I'd forgotten that with the Branded Zones some native features are actually handled by the underlying global zone (i.e. Solaris 10).
Anyway, has anybody else had this same problem and how did you resolve it?
Thanks
Tim Shaw.

I found out that the services in the Global Zone had been disabled. Simply enabling them fixed the problem :)

Problems with rsh in solaris 8

I have tried to execute a command with "rsh", like a "prstat", and it works but if I execute a "snoop" command, I see that the machine that runs the command(rsh) lost information. There is packets from TCP that has been return (in some occasions partially), this provokes the application losts information.
Which can the problem be ?

OK, but the problem is not in C++. Your C++ code just invokes invokes the shell and remote operations, and returns the result. The local C++ program cannot cause or repair communication problems between machines.

Rsh in solaris

hi guys
we have moved our apps and db servers physically
my solaris admin had earlier made a shell script for daily backup of prod system. since we have 2 node configuration,he is calling the second node from 1 st node to stop the apps services. however the rsh command is giving timeout.
he is using the following line in script
"rsh prdap -n '/tmp/stopapp.sh >/dev/null 2>&1 </dev/null &'"
I want to know where is prdap defined as alias for the ap server.
more hosts --
127.0.0.1 localhost
10.224.8.142 faprdap.sog.com faprdap
192.168.0.2 prdap
on faprdap.sog.com
more .rhosts
faprddb.sog.com root
prddb root
However, the apps server is faprdap.I was wondering y he is calling the "prdap" and it was working fine.
Any help would be appreciated
Anmol
...

As I understand from your post:
- Application node hostname: prdap
- Application node IP Address: 192.168.0.2
- Database node hostname: prddb
- Database node IP Address: Unknown
Your DBA is calling "stopapp.sh" script from the database node to stop the application services using "rsh prdap -n '/tmp/stopapp.sh >/dev/null 2>&1 </dev/null &'"
faprdap, and faprddb are private interconnect hostnames (addresses) for the application node and the database node respectively which are used for the cluster purpose.

Compatibility issues between solaris 10 patches and Weblogic server 9.2

Is there any documentation about possible incompatibility between certain solaris patches and Weblogic server?

Hi,
Can you post the output of below commands from your OS?
uname -a
getconf LONG_BIT
Do you want to download and install 64-bit WLS 9.2 on your OS?
- - Tarun

Differences between solaris Intel and solaris Sparc

Hi,
I'm new to this solaris world. But I've been using other flavour of unix. I just wondering if somebody could explain to me the differences between Intel version and Sparc version, please? If you have any website that explain it all would be great.
Thank you in advance.
regards,
zonex

It's more of a question of what architecture you would run it on. But a few things software wise:
SPARC has 64-bit OS support
SPARC generally has more 3rd party software available
SPARC is supported by Sun, Intel is being phased out
Intel I percieve as faster than lower-end SPARC
They are not binary compatible, so you can't run SPARC binaries on Intel and vice versa.

RSH between Solaris 8 & 9

Similar Messages

Maybe you are looking for