mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Burns <sburns@webzone.net>
To: linux-kernel@vger.kernel.org
Date: Mon, 09 Apr 2001 17:28:12 -0500	[thread overview]
Message-ID: <5.0.2.1.2.20010409171526.00aba108@pop3.webzone.net> (raw)

Group,

Here's my last try.  I've edited all of the headers (sched.h, param.h, 
limits.h) in /usr/include and /usr/src/linux, I've recompiled the 
shadow-utils and PAM.  My limit is still 32.  Am I missing something - 
obvious?  I did go ahead and upgrade to glibc-2.2-12 and kernel 2.4.3 (with 
edited headers) to no avail.  This has been a really bad problem, I greatly 
appreciate any help at all.  (thanks Jeff Garzik for your 
suggestion).  BTW, please CC me directly.

Stephen

Stephen Burns wrote:
 >
 > Hey all,
 >
 > I have checked out the archives, and I found an old post regarding this.
 > The solution in the post, however, did not work for me. I am attempting to
 > raise the maximum 32 group per user limit on my 2.4.2 kernel. I patched
 > both linux/include/linux/limits.h and the asm-i386/param.h, replacing the
 > default "32" with "256." My glibc is 2.1.2. When I make clean, and
 > recompile the kernel, it boots fine but I am still limited to 32 groups. I
 > don't need to do anything with glibc since it is of the 2.1 or greater
 > category, correct? Any ideas, hints, tricks? Thanks a ton for your help,
 > please CC me as I've not been approved yet as a member of this list.

You gotta change the task struct...

-- 
Jeff Garzik       | Sam: "Mind if I drive?"
Building 1024     | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft      |       and shrieking like a cheerleader."


                 reply	other threads:[~2001-04-09 22:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.0.2.1.2.20010409171526.00aba108@pop3.webzone.net \
    --to=sburns@webzone.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®