Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!bloom-beacon!world!madd
From: madd@world.std.com (jim frost)
Newsgroups: comp.unix.aix
Subject: Re: Connectivity problems With IBM
Message-ID: <1990Aug23.124525.10764@world.std.com>
Date: 23 Aug 90 12:45:25 GMT
References: <1990Aug12.031309.15691@maverick.ksu.ksu.edu> <6101@hub.ucsb.edu> <3143@awdprime.UUCP>
Organization: Saber Software
Lines: 26

In article <6101@hub.ucsb.edu> erickson@pollux.ncgia.ucsb.edu (Scott Erickson) writes:
>I find that (on IBM RT's, PS/2's, and RS6000's) IBM tends to make
>their software so that it's easy to connect with other IBM machines,
>but it's extremely painful to connect to anything else!

We ran into a neat one yesterday.  If your root shell is /bin/ksh (the
default) and a user's home directory is NFS mounted (most of our users
are on a Sun-4/330 under 4.0.3c) and the user "su"'s to root, ksh will
start making tons of NFS requests across the network.  It will flood
the network, thus inhibiting everyone's communication, and bring the
foreign server to its knees (biod's will be running all-out).

Killing the ksh process started by "su" causes the problem to go away.
Changing the root shell to /bin/csh eliminates it entirely.

This problem exists under 9021F with the 3001 update installed.  We
never noticed it before the 3001 update so I believe the update caused
the problem (might be wrong though).

This problem has been reported to IBM.

Informationally yours,

jim frost
saber software
jimf@saber.com