Bug 5564 - Users using RXVT, gnome-terminal, Eterm and KVT are NOT shown under who or w command
Users using RXVT, gnome-terminal, Eterm and KVT are NOT shown under who or w ...
Product: Red Hat Linux
Classification: Retired
Component: rxvt (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Preston Brown
: Security
Depends On:
  Show dependency treegraph
Reported: 1999-10-05 01:57 EDT by mbartsch
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-13 21:55:19 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 mbartsch 1999-10-05 01:57:42 EDT
i assigned it under rxvt, maybe it is a utemper or glibc
problem, but as i don't had more information i just put it
under rxvt...

under Lorax 6.0.55 when you use a Eterm or gnome-terminal,
and you use who or w command, you can see what PTY you had
assigned, under 6.1 (Update From 6.0.55) the didn't
show up, but PTY are allocated.

[synflood@ENDOR RPMS]$ ls -al /dev/pts/
total 36
drwxr-xr-x   2 root     root            0 Oct  5 01:06 .
drwxr-xr-x   5 root     root        36864 Oct  5 01:06 ..
crw--w----   1 synflood tty      136,   0 Oct  5 01:54 0
crw--w----   1 synflood tty      136,   1 Oct  5 01:54 1
but who or w only shows the users at the VT's not the PTY's

[synflood@ENDOR RPMS]$ w
  1:55am  up 49 min,  2 users,  load average: 0.10, 0.30,
USER     TTY      FROM              LOGIN@   IDLE   JCPU
root     tty1     -                 1:06am 20:09   0.12s
0.11s  -bash
synflood tty2     -                 1:06am 47:26  47.45s
0.01s  startx

Any comment please e-mail me for more details..
Comment 1 Preston Brown 2000-01-13 21:55:59 EST
these terminals need to be explicitly told to make utmp entries.  For instance,
on gnome-terminal, do

gnome-terminal --utmp

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