| Summary: | [libc] [patch] getgrent() does not return large groups via NIS | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Kirk Webb <kwebb> | ||||
| Component: | bin | Assignee: | Marcelo Araujo <araujo> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | araujo, tcleamy | ||||
| Priority: | Normal | ||||||
| Version: | 6.0-RELEASE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Kirk Webb
2006-05-05 23:40:14 UTC
Hi, I encountered with bug again in last month. This patch (reversed) help me. Thx. Why this patch in not HEAD? -- Andrey Zonov State Changed From-To: open->analyzed Another contributor notes that this patch helps. I just ran across this bug in FreeBSD 9.2 amd64. The odd thing is that I'm migrating from 8.3 i386 and those systems don't have the issue with the same NIS maps. So it worked for me on FreeBSD 8.2 i386 & 8.3 i386, but not 9.2 amd64. Go figure. I figured I should email in to push to get this patch added into the releases. The patch work for me although the line numbers were off by ~120. I guess a bit of code has been added since FreeBSD 6. Tim Leamy UC Davis Oops... Looks like the fix didn't get pulled upstream! We're moving to 9.x soon, so I appreciate the heads up. -Kirk On Fri, Feb 28, 2014 at 3:28 PM, Tim Leamy <tcleamy@ucdavis.edu> wrote: > I just ran across this bug in FreeBSD 9.2 amd64. The odd thing is that I'm > migrating from 8.3 i386 and those systems don't have the issue with the same > NIS maps. So it worked for me on FreeBSD 8.2 i386 & 8.3 i386, but not 9.2 > amd64. Go figure. > > > > I figured I should email in to push to get this patch added into the > releases. The patch work for me although the line numbers were off by ~120. > I guess a bit of code has been added since FreeBSD 6. > > > > Tim Leamy > > UC Davis It was fixed while ago already. Thanks for the patch. I don't think this is fixed. I ran into the problem on 10.3 AMD64. The NIS group was 616 chars long and failed to appear in "groups <user>". I applied the patch and it resolved the issue. |