🚀 go-pugleaf

We have a 3-level netinfo network with about four midlevel application
servers and 60 machines.  Most user definitions and home mounts are at
the top level.  I thought I'd be least disrup.tive to upgrade to 3.0
from the bottom up.  Upgrading a couple of lowest level machines
worked fine.  But when I upgraded a midlevel host (in place, not
from a clean disk), access problems occur.  Users with homes in
the midlevel's domain still work ok, but users with homes elsewhere
cannot access their homes.  They can login, but get a blank screen.
Root can see the list of homes on a remote file system, but can't go
further down as it could before.
 
Here's a representative fstab entry from the top level:
     mugcnx1:/Users /Net nfs rw,net,timeo=14,intr,noquota 0 0
 
Here's the 2.0 exports line:
     /Users -access=allmunx,root=mugcnx1:mugcnx2:muebnx1:     ...etc..
 
mugcnx1 is the 2.0 toplevel, muebnx1 is the 3.0 midlevel.
 
Another irritating thing.  In using UserManager.app from the 3.0 midlevel
host to a 2.1 toplevel netinfo passwd server, the app locks.  "ps" shows
it is trying to readUserLanguage.  3.0 netinfo data for user adds an
"info" directory, and it looks like UserMangler is trying to access a
dwrite for System Language--somewhere.
 
I guess I'll go ahead and upgrade the toplevel server, and hope that
this will solve the problems.  I hope this is not some idiot little
item this idiot has overlooked, or that somewhere it says "upgrade
networks from the top down".  For the curious, I can provide nidump &
nilist output.  If anybody has insight,reply direct, I'll summarize.
If anybody is contemplating a similar upgrade, well, stay tuned.
 
:  Greg Johnson, Senior Scientific Programmer/Analyst -- Campus Computing
:  233 Heinkel Building, University of Missouri, Columbia, MO 65203
:  ccgreg@mizzou1.missouri.edu / ccgreg@monad.missouri.edu / 314-882-2000