This is IOT-Trap-from-rusers-and-mount-t-nfs? in view mode; [Up]
Date: Sun 11-Dec-1989 02:08:15 From: Unknown Subject: IOT Trap from rusers and mount -t nfs? 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. -=EPS=- >From: epsilon@wet.UUCP (Eric P. Scott)
Date: Sun 11-Dec-1989 04:25:16 From: Unknown Subject: Re: IOT Trap from rusers and mount -t nfs? root is in 9 groups on the machine in question. -=EPS=- >From: dyer@spdcc.COM (Steve Dyer)
Date: Sun 11-Dec-1989 08:19:54 From: Unknown Subject: Re: IOT Trap from rusers and mount -t nfs? 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.
Date: Sun 11-Dec-1989 12:12:28 From: Unknown Subject: Re: IOT Trap from rusers and mount -t nfs? 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. > > -=EPS=- I am having similar problems, we have two cubes each with 330 meg drives so instead of havein NextLibrary(110meg) on both I cross mounted from on to the other. But I want to cross mount /usr/local back to the other cube (the one with NextLibrary) but no dice. The question is why can I mount from one to the other but then not vice versia. Also the only way I can get the mount to work is at boot time whenever I mount -a or mount /usr/local jeckle:/usr/local I get IOT trap (hmm I don't know) I think all the file are correct. because we also mount user space from our sun cluster. <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> <> :-{ :-\<> Russell Cattelan University of Minnesota <> <> :-} :-`) <> cattelan@umn-cs.cs.umn.edu <> <> :-) :-( <> {...!rutgers!umn-cs!cattelan} <> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >From: cox@Franz.COM (Charles A. Cox)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.