Bug 42850
Summary: | sessreg broken with high UID's | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | panu.matilainen | ||||
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 7.2 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2002-04-11 15:13:45 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
panu.matilainen
2001-05-30 12:51:07 UTC
Deferring for future investigation. Since nobody else seems interested ;) I took a further look at this. There's nothing fundamentally wrong with sessreg itself, the problem lies in the lastlog mechanism/fileformat where the file grows too large for even 64bit offsets to handle with big enough UIDs. Login & friends actually have the same problem but it doesn't normally show up because it doesn't check for errors like sessreg does. Created attachment 50464 [details]
patch to workaround the high uid problem
Soo typical.. just after posting the earlier comment I realized it's just not using the 64bit interface. Attached patch works around it but that's the way to do it - I guess this is just some kind of linking problem. AND this affects every RH 7.x release, Skipjack included. Pretty please fix it for Skipjack / whatever comes after it. Refiled this against skipjack2 and closing this one (I'm not expecting a fix for the old releases..) Just a note for the future... Instead of opening a new report, you can just update an existing report with new information, and update the product/version instead if you prefer. Either way is fine however. Marking as a dupe of the new report, which is fixed in RAWHIDE XFree86 4.2.0-6.63 and later. Thanks. *** This bug has been marked as a duplicate of 61136 *** ARGH. Closed as dupe of wrong bug. |