home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!menudo.uh.edu!menudo.uh.edu!usenet
- From: sears@tree.egr.uh.edu (Paul S. Sears)
- Newsgroups: comp.sys.next.sysadmin
- Subject: Re: Next 2.{1,2}: any user logging in becomes root?! [netinfo?]
- Date: 16 Nov 1992 14:19:01 GMT
- Organization: University of Houston
- Lines: 33
- Message-ID: <1e8aklINNjto@menudo.uh.edu>
- References: <16986@umd5.umd.edu>
- Reply-To: sears@tree.egr.uh.edu
- NNTP-Posting-Host: thanatos.egr.uh.edu
-
- In article <16986@umd5.umd.edu> matthews@oberon.umd.edu (Mike Matthews)
- writes:
- =>In article <1992Nov13.000853.28574@kakwa.ucs.ualberta.ca>
- sherwood@space.ualberta.ca (Operator) writes:
- =>> I suspect that this machine is not mounting the user's file system
- =>
- =>That was what I thought too, and is usually the case. Then the same thing
- =>happened to me. The user who logs in, even with their own userid/password,
- =>is root as far as 'whoami' is concerned.
- =>
- =>The problem is with lookupd; when it gets hosed Really Bad Things like this
- =>start to happen.
- =>
-
- So I guess that I am not the only one who is having severe problems with
- lookupd. After much investigation, it seems that if you have netgroups set up
- incorrectly (if you are using them) in netinfo, lookupd can get hosed rather
- easily. What complicated our problem was that we had two servers serving our
- cluster...
-
- =>>=> Sherwood Botsford sherwood@space.ualberta.ca <=
-
-
- =>Mike Matthews, matthews@oberon.umd.edu (NeXTmail accepted)
- =>------
-
- --
- Paul S. Sears * sears@uh.edu (NeXT Mail OK)
- The University of Houston * suggestions@tree.egr.uh.edu (NeXT
- Engineering Computing Center * comments, complaints, questions)
- NeXT System Administration * DoD#1967 '83 NightHawk 650SC
- >>> SSI Diving Certification #755020059 <<<
- "Programming is like sex: One mistake and you support it a lifetime."
-