Bug 84026 - gdm does not update /var/run/utmp correctly
gdm does not update /var/run/utmp correctly
Status: CLOSED DUPLICATE of bug 101105
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
8.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Mike McLean
: Triaged
Depends On:
Blocks: 79579 CambridgeTarget
  Show dependency treegraph
 
Reported: 2003-02-10 21:59 EST by Norman Gaywood
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-10 15:44:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Norman Gaywood 2003-02-10 21:59:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
gdm does not update /var/run/utmp correctly when logging in via xdmcp. The first
user seems to be added correctly but all subsequent logins replace the previous
login. So 'who/w/finger' only ever shows one X terminal style login even though
there are many more.

wtmp seems to be correct. That is, last correctly shows that last and current
logins.

The only changes I have made to the gdm setup from a default install is to the
gdm.conf file. Here is the diff between my gdm.conf and the one supplied in RH 8.0

diff gdm.conf gdm.conf-redhat
72c72
< Enable=true
---
> Enable=false
74,78c74,78
< MaxPending=10
< MaxPendingIndirect=10
< MaxSessions=80
< MaxWait=30
< MaxWaitIndirect=30
---
> MaxPending=4
> MaxPendingIndirect=4
> MaxSessions=16
> MaxWait=15
> MaxWaitIndirect=15
149c149
< #0=Standard
---
> 0=Standard


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Make changes to gdm.conf to allow xdmcp logins
2. restart gdm
3. start logins from 2 or more xterminals via xdmcp and observe the output of
who/w/finger
    

Actual Results:  Only the last xdmcp login is displayed with who/w/finger even
though the last command shows more than one "still logged in".

Expected Results:  All users should be in who/w/finger output

Additional info:
Comment 1 George Lebl 2003-07-23 15:20:14 EDT
Note that this is the way that the redhat package handles the Pre/PostSession
scripts.  upstream will handle this correctly.
Comment 2 George Lebl 2003-08-04 15:01:03 EDT
Hmmm, apparently recent RPMS do this correctly, but I think if you upgrade from
a version that did it wrongly (don't know which was the last version that did
that) you might still get wrong links in the PreSession/PostSession dirs.  See
bug #101105 since that's related (well really the same exact problem I think).
Comment 3 Ray Strode [halfline] 2004-11-10 15:44:48 EST

*** This bug has been marked as a duplicate of 101105 ***

Note You need to log in before you can comment on or make changes to this bug.