Solaris to solaris unstable, Solaris to HPUX stable??

Solaris to solaris unstable, Solaris to HPUX stable??

Post by Paul Newhou » Sun, 23 Jul 2000 04:00:00

Sorry if this is a well know mistake, but I just don't get it.

  +---------+              +---------+
  |         |              |         |
  |  NetBSD +--------------+  NetBSD |
  |    F    |              |    H    |
  +----+----+              +---------+
  |         |
  | Solaris +-----+-------------------------------+
  |    W    |     |                               |
  +---------+     |                               |
                  |                               |
             +----+----+                     +----+----+
             |         |                     |         |
             | Solaris |                     |  HP-UX  |
             |    X    |                     |    Y    |
             +---------+                     +---------+

Solaris-W ipnat's the NetBSD-H address to a logical address (hme1:1)
on Solaris-W, and NetBSD-F to hme1:2.

If I:

    rlogin Solaris-W
    rlogin HP-UX-Y

from my home machine (NetBSD-H) the session is stable and stays
up as long as the tunneled pppd connection is viable.

If I:

    rlogin Solaris-X
    rlogin Solaris-W
        and then rlogin Solaris-X

I can hang the session pretty easily.  These sessions seem to be very
unstable.  It is very easy to hang the session with an ls that produces
more than one screen of data, or using "more" with just about any amount
of data.  In the second example, if I break out of the session with ~.,
so that I'm back on Solaris-W, that session seems stable and continues to
work fine.  From NetBSD-H I can:

    rlogin Solaris-X
    rlogin HP-UX-Y

and get the same results over and over (Solaris seems flakey, HPUX
seems stable).

If I'm directly on Solaris W (using the directly connected monitor)
connections to Solaris-X and HP-UX-Y seem very solid.

I'll gladly post any relevant stuff.  There is so much that it could
be I hesitate to dump it all in here to start.  The path is common
until it is sent out on the wire to X & Y.  

I'm suspicious that it is some setting on X or some interaction between
the settings on W & X, but I'm pretty baffled about this and have nary a
clue where to start looking.

Hints/clues/solutions anyone?

Paul Newhouse

The lotto must be rigged, I should have won by now.
Modular furniture is cruel and unusual.


1. Upgrading to Solaris. Is Solaris 2.3 stable?

I read some articles about SunOS4.1.3 vs. Solaris 2.3.
I also have a plan to upgrade my system (SunOS 4.1.1) to SunOS 4.1.3 or Solaris 2.3.
I understand that SunOS 4.1.3 is dead end, and Solaris is better.
But I heard from someone that Solaris is unstable and tend to down.
Is it true?
Any response will be appreciated. Thank you in advance.



2. changing date to a file

3. SunOS 5.6 vs Solaris 2.6 vs Solaris 7 vs Solaris 8

4. *UNIX developers - Wall St - Big $*


6. Solaris 7 SERVER Sparc for $99: Good Price?

7. quota problems between solaris and solaris machines, and solaris and sunos4.1.3 machines.

8. Any upgrade gotchas for RH 9?

9. Solaris 10 (build 63) upgrade fails on Solaris 8 as well as Solaris 9 sparcs

10. Solaris iNtel *is* very unstable [WAS: Re: what happens to the web at 2am?]

11. Solaris "msc" equivalent for HPUX 10.*

12. HPUX and Solaris

13. Help with mounting CD on Sun Solaris and HPUX!!!!