[Samba] AD group membership limits?
Simon.Gibbs at informa.com
Wed Mar 9 18:04:55 GMT 2005
I've just attempted to apply (in dry-run mode) the supplied kernel patch but
received a number of errors. Does anyone know if these are critical errors?
Here is the output:
[ukfs02 linux-2.4]# patch -p1 --dry-run -i more_groups_simple.patch
patching file arch/i386/kernel/init_task.c
Hunk #1 succeeded at 11 with fuzz 2 (offset 1 line).
patching file arch/s390/kernel/init_task.c
Hunk #1 succeeded at 17 with fuzz 2 (offset 1 line).
patching file include/asm-i386/param.h
patching file include/asm-i386/processor.h
Hunk #1 FAILED at 452.
1 out of 1 hunk FAILED -- saving rejects to file
patching file include/asm-s390/param.h
Hunk #1 succeeded at 19 (offset 3 lines).
patching file include/asm-s390/processor.h
Hunk #1 FAILED at 144.
1 out of 1 hunk FAILED -- saving rejects to file
patching file include/linux/limits.h
patching file include/linux/mm.h
Hunk #1 FAILED at 454.
1 out of 1 hunk FAILED -- saving rejects to file include/linux/mm.h.rej
patching file include/linux/sched.h
Hunk #1 succeeded at 520 (offset 146 lines).
Hunk #2 succeeded at 546 (offset 76 lines).
Hunk #3 FAILED at 587.
Hunk #4 succeeded at 1143 (offset 196 lines).
1 out of 4 hunks FAILED -- saving rejects to file include/linux/sched.h.rej
patching file kernel/fork.c
Hunk #1 FAILED at 580.
Hunk #2 FAILED at 601.
2 out of 2 hunks FAILED -- saving rejects to file kernel/fork.c.rej
patching file kernel/sched.c
Hunk #1 FAILED at 1314.
1 out of 1 hunk FAILED -- saving rejects to file kernel/sched.c.rej
patching file mm/page_alloc.c
Hunk #1 FAILED at 439.
1 out of 1 hunk FAILED -- saving rejects to file mm/page_alloc.c.rej
> From: <Gibbs>, Simon <Simon.Gibbs at informa.com>
> Date: Wed, 09 Mar 2005 16:19:22 +0000
> To: "Kaplan, Marc" <marc_kaplan at adaptec.com>, <samba at lists.samba.org>
> Subject: Re: [Samba] AD group membership limits?
> Thanks for the info (and sorry about my delay in posting back).
> I've just tested FC3 running the 2.6 kernel and it does resolve the issue. So
> in an ideal world I'd prefer to wait for RHEL4 but because of required third
> party drivers and apps that are required it looks like I'm going to have to
> recompile with the patches.
> I've downloaded the patches from the paths you gave me but I'm not to sure how
> to apply them as I've never had to do anything like this before.
> Have you (or anyone else out there) got any good pointers - specifically for
> these patches.
> Thanks for your help.
>> From: "Kaplan, Marc" <marc_kaplan at adaptec.com>
>> Date: Wed, 2 Mar 2005 13:24:28 -0800
>> To: "Gibbs, Simon" <Simon.Gibbs at informa.com>, <samba at lists.samba.org>
>> Subject: RE: [Samba] AD group membership limits?
>> Yes, I have recompiled the kernel with support for a static NGROUPS with
>> a patch from tridge and Rusty Russell. This does not seem to cause any
>> problems at all on Samba servers, or with the Linux box in general and
>> it does properly allow more supplementary groups.
>> Here is what I used IIRC:
>> Though I just checked on this, and maybe support for dynamic NGROUPS is
>> now in the 2.6 kernel? See:
>>> -----Original Message-----
>>> From: samba-bounces+marc_kaplan=adaptec.com at lists.samba.org
>>> bounces+marc_kaplan=adaptec.com at lists.samba.org] On Behalf Of Gibbs,
>>> Sent: Wednesday, March 02, 2005 2:58 AM
>>> To: samba at lists.samba.org
>>> Subject: [Samba] AD group membership limits?
>>> I'm running Samba 3.0.11 on RedHat ES 3 kernel version
>>> and have a quick question about AD group membership limits
>>> Am I right in assuming that Samba is limited by the group membership
>>> parameters (ie NGROUP = 32) imposed by the Linux kernel? Is there any
>>> workaround in Samba for this?
>>> At the moment if a user is a member of more then 32 domain groups they
>>> cannot access any shares. If I remove some of the groups to below the
>>> group limit everything is fine.
>>> If there isn't a workaround in Samba has anyone reliably recompiled
>>> kernel and run Samba after changing the group parameters?
>>> I guess this must be a fairly common problem in a lot of sites?
>>> Any help with this much appreciated.
>>> The information contained in this email message may be confidential.
>>> you are not the intended recipient, any use, interference with,
>>> or copying of this material is unauthorised and prohibited. Although
>>> message and any attachments are believed to be free of viruses, no
>>> responsibility is accepted by T&F Informa for any loss or damage
>>> in any way from receipt or use thereof. Messages to and from the
>>> are monitored for operational reasons and in accordance with lawful
>>> business practices.
>>> If you have received this message in error, please notify us by return
>>> delete the message and any attachments. Further enquiries/returns can
>>> sent to postmaster at tfinforma.com
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/listinfo/samba
More information about the samba