https://bugzilla.novell.com/show_bug.cgi?id=396100 Summary: gdm still doesn't honor MaxSessions and DisplaysPerHost Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: qa@suse.de Found By: Customer In /etc/gdm/custom.conf or /usr/share/gdm/defaults.conf, in the [xdmcp] section, if MaxSessions or DisplaysPerHost are set (and gdm is signalled or restarted), even so the hardwired defaults of 16 and 2 respectively are used. Other hardwired defaults may also be not getting honored but I only need, and tested, these two. Both files are actually being read, judging from their atime. http://ftp.gnome.org/pub/GNOME/desktop/2.22/2.22.2/NEWS (dated 2008-05-28) says about gdm-2.20.6: Fix so that the XDMCP configuration values are read from the configuration file when the XDMCP manager is started rather than initialized. It seems the related fixes implemented in 2.20.2 did not fully resolve this issue. (Brian Cameron) If this fix could be propagated into SuSE that would be greatly appreciated on our shared execution servers, which are managing sessions from multiple Windows clients. We're currently using hpjansson's gdm-2.20.4-1.1 for 11.0-testing, which avoids a file descriptor leak and/or failure to decrement the session count on logout, so our situation is improved but more improvement is hoped for. I see the same behavior in gdm-2.20.0-8.2, 8.4 and 8.5. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.