Bug 431852
| Summary: | gdm 2.20.2/3 ignores MaxSessions value | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Steve Bergman <sbergman> |
| Component: | gdm | Assignee: | jmccann |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | cschalle |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-01-09 05:56:26 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: | |||
|
Description
Steve Bergman
2008-02-07 12:52:01 UTC
I just noticed I have a typo in the subject. Just to be clear, I am using MaxSessions as the key and not MxSessions. Also, the fork bomb problem on build went away and I have a special version compiled with MaxSessions hardcoded to 100. Did a gdm-safe-restart and probably won't be certain whether it works until after close of business today. Well, my new rpm in which I hardcoded Maxsessions=100 into daemon/gdm-daemon-config-keys.h still rejects clients at about the same number and emits the maximum sessions reached message. I'm stumped. There have been two recent (oct/nov 2007) issues which might relate. One in which the config files were not being honored for certain config keys. And another where the counter was not getting decremented properly. I know the latter is not the case here, since I have only about 18 users doing xdmcp sessions. Everyone else is using NX. And the former should have been worked around by my hardcoding the values. This is a fresh 64 bit install. It seems odd that no one else has reported this problem. Turning on debug I see that Maxsessions is always 16. The session count seems to increment and decrement properly, so the only problem seems to be MaxSessions being stuck at 16. Setting: #define DEFAULT_MAX_DISPLAYS 64 in daemon/gdm-xdmcp-manager.c and recompiling *does* give me 64 sessions. So that's a work around, and perhaps a clue as to where the real problem is. I'm a bit confused, since I thought all this got hashed out and fixed upstream in 2.20.2 months ago. But downloading the vanilla source from upstream and compiling yielded the same broken behavior. This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |