Bug 476780 - procps - uptime displays wrong # of users
procps - uptime displays wrong # of users
Product: Fedora
Classification: Fedora
Component: procps (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Daniel Novotny
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-16 21:52 EST by Tom Broadhurst
Modified: 2009-12-18 02:18 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:18:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom Broadhurst 2008-12-16 21:52:10 EST
Description of problem:
Both uptime and w display the wrong number of users.

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

How reproducible:
Every time

Steps to Reproduce:
1. From a clean boot in run level 3, login root on tty1, execute w
2. Login a different user on tty2
3. Execute w
4. Logout of tty2
5. Execute w from tty1
6. Continue from step 2, number of users keeps incrementing.
Actual results:
[root@xxx ~]# w
 21:31:34 up 1 min, 1 user, load average: 0.73, 0.25, 0.08
USER     TTY      FROM            LOGIN@   IDLE   JCPU   PCPU WHAT
root     tty1     -              21:31    0.00s  0.02s  0.00s w
[root@xxx ~]# w
 21:37:09 up 6 min, 2 users, load average: 0.00, 0.07, 0.05
USER     TTY      FROM            LOGIN@   IDLE   JCPU   PCPU WHAT
tom      tty2     -              21:37    5.00s  0.02s  0.02s -bash
root     tty1     -              21:31    0.00s  0.02s  0.00s w
[root@xxx ~]# w
 21:31:34 up 10 min, 2 users, load average: 0.00, 0.03, 0.03
USER     TTY      FROM            LOGIN@   IDLE   JCPU   PCPU WHAT
root     tty1     -              21:31    0.00s  0.02s  0.00s w
[root@xxx ~]# w
 21:42:57 up 12 min, 3 users, load average: 0.00, 0.01, 0.02
USER     TTY      FROM            LOGIN@   IDLE   JCPU   PCPU WHAT
root     tty1     -              21:31    0.00s  0.02s  0.00s w
tom      tty2     -              21:42    4.00s  0.02s  0.02s -bash

Expected results:

Additional info:
Comment 1 Tom Broadhurst 2008-12-20 12:03:09 EST
On Dec 12, 2008, with only root logged onto tty1, the following output was displayed.

[root@xxx ~]# who
root     tty1     2008-12-20 07:58
[root@xxx ~]#
[root@xxx ~]# cat /proc/key-users
    0:     6 5/5 3/200 85/20000
[root@xxx ~]#
Comment 2 Bug Zapper 2009-11-18 05:29:41 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 
Comment 3 Bug Zapper 2009-12-18 02:18:58 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

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