[OpenAFS] setpag: Invalid argument + fledgling documentation

[ted creedon]

The "fledgling documentation effort" is experimenting with pdf-xml-LateX
transformations. Xml can be served up directly by platform.

One of the nice things about IBM's docs is that they cover all platforms but
in an unwieldly single document. The reduction of the quick start guide to a
Linux only (as a test) is very attractive. About a 5:1 reduction in content.

Once we get the proofreading done I forsee a "catch up" effort with an N:P
data hassle. N = the number of text formats and P = the number of supported
platforms.

The IBM docs are 5 years old.

I'll post an progress info later this week.

Tedc


-----Original Message-----
From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org]
On Behalf Of Derrick J Brashear
Sent: Tuesday, January 18, 2005 1:10 PM
To: openafs-info@openafs.org
Subject: Re: [OpenAFS] setpag: Invalid argument

On Tue, 18 Jan 2005, John Tang Boyland wrote:

> I'm using OpenAFS 1.2.10 on Solaris 8.  A strange thing had been
happening:
> pagsh didn't work anymore.  I had a long-going console login (with a 
> PAG) and within it, a shell that was running a pagsh with a different 
> pag, but I wasn't able to start up new pagsh's, I got the message:
> 	setpag: Invalid argument
> and no PAG is created.  I tried rebooting, but then I couldn't get any 
> PAGs at all.
>
> But with some experimentation, I found out what was happening: my 
> username was in too many UNIX groups: 15.  When I cut the number of 
> groups down to 11, the problem went away, and I was able to get a PAG.
> I found:
> /usr/include/limits.h:#define   NGROUPS_MAX     16
> That explains it.  Should this setpag behavior be documented somewhere?

Probably. The question is, where?

Perhaps the fledgling documentation effort should have an RT queue where
stuff like this should go? I'm not volunteering them for it, but it's a
thought.

_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info