Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!spdcc!dyer
From: dyer@spdcc.COM (Steve Dyer)
Newsgroups: comp.sys.next
Subject: Re: IOT Trap from rusers and mount -t nfs?
Message-ID: <836@ursa-major.SPDCC.COM>
Date: 11 Dec 89 08:19:54 GMT
References: <857@wet.UUCP>
Reply-To: dyer@ursa-major.spdcc.COM (Steve Dyer)
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 21

In article <857@wet.UUCP> eps@cs.sfsu.edu (Eric P. Scott) writes:
>Any ideas what would cause this--or what I should look for?
>Only one cube does it.
>
>rusers (with no arguments) dies with an IOT Trap, but works
>fine when given a hostname.  NFS mounts also die with IOT
>Trap.  My guess is there's a "this can't ever happen" abort()
>somewhere (in the RPC code?).  I'm stymied.

I'm not a NeXT expert, but I'm familiar with the Sun RPC library.
abort() is called within auth_unix_create_default() if the
getgroups() call returns -1.  This will occur if the RPC library
called getgroups(ngroups, ...) with a value of ngroups smaller
than the kernel value (i.e. if the library was compiled with
NGRPS set to 8 but the kernel thinks that NGROUPS is larger, say,
16 or 32.

-- 
Steve Dyer
dyer@ursa-major.spdcc.com aka {ima,harvard,rayssd,linus,m2c}!spdcc!dyer
dyer@arktouros.mit.edu, dyer@hstbme.mit.edu