Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 48586 - > coreutils-5.2.0 utmp users who relic problem
Summary: > coreutils-5.2.0 utmp users who relic problem
Status: RESOLVED DUPLICATE of bug 49175
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-21 11:42 UTC by Derk W te Bokkel
Modified: 2005-07-17 13:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Derk W te Bokkel 2004-04-21 11:42:10 UTC
using the users command or using gkrellm monitoring I'm seeing extra user logins for every terminal process in a  logged in xsessions (running kde-3.2.2 fluxbox or xcfe or gnome 2.6.0/1) has the handling of child processes changed? Also every logged in X user has two users associated with it .. for each login .. any idea why .. ?

I'd expect to see just one user listed for the master login .. how to fix?



Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Aron Griffis (RETIRED) gentoo-dev 2004-04-21 12:05:14 UTC
man xterm, search for -ls, fix in .Xdefaults or on the command-line.
This is a bug-reporting system, please take questions like this to either the forums or the appropriate mailing list.
Comment 2 Aron Griffis (RETIRED) gentoo-dev 2004-04-21 12:24:09 UTC
My apologies, I came down too hard in my last comment.  What I meant is something like this:  The behavior you're describing is not a bug, but is expected behavior based on the configuration of your system.  Please ask around in the forums or mailing lists prior to assuming you've found a bug.  That would allow us to concentrate on fixing the things that are really bugs instead of answering questions.  Thanks!
Comment 3 Derk W te Bokkel 2004-04-21 14:23:01 UTC
It effects  two out of four of my systems which were fine before ..
and yes I did search the forums and the bug reporting system

and for some reason I got dropped off the mailing lists I was on ..

The fact that the behaviour changed without notice concerns me .. 

also where do you set the global/system wide .Xdefaults I know .. question for else where .. i'm just a wee bit perturbed by the unexpected change

Note: This also a non-X problem I'm seeing the same thing at the consoles login on a machine once and you're there as two users ..
Comment 4 Derk W te Bokkel 2004-04-21 15:33:55 UTC
my apologies .. second console login was traced to an orphaned process .. bonobo-activation still running as the user. My appologies again ..

I still can't understand why the defaults have changed. There are no .Xdefault files in sight in any directories, and it effects all users.

by the way I'm using xorg-x11 (on all 4 machines) not xfree and things may be different in that environment. However it was just fine until yesterday when coreutils was upgraded as well as kde, some gnome, some xfce but not flux box. which is why I suspected coreutils as the effect is for all of them. None of these  should have touched the core X settings.

but I'll keep fishing sorry to have bothered you.
Comment 5 Derk W te Bokkel 2004-05-26 17:05:23 UTC
Okay my fishing expedition was rather circular but here goes ..

all programs in coreutils relying on utmp appear to have the same defect ..
if a terminal program or other process dies then it leaves a relic in utmp with no regular logout this is visible in a 'last' command as follows (with some snips to remove extraneous data)

last -50
hannah   pts/194                       Wed May 26 16:18 - 16:27  (00:08)
hannah   zwift.zapvil zwift.zapville.o Wed May 26 16:18 - 16:27  (00:08)
nick     pts/193                       Wed May 26 16:18 - 16:26  (00:08)
nick     znark.zapvil znark.zapville.o Wed May 26 16:18 - 16:26  (00:08)
snip ..
derk     pts/189                       Wed May 26 15:58 - 16:21  (00:23)
hannah   pts/188                       Wed May 26 15:50    gone - no logout
hannah   zwift.zapvil zwift.zapville.o Wed May 26 15:50 - 15:50  (00:00)
derk     pts/187                       Wed May 26 15:42 - 16:22  (00:39)
..snip
derk     pts/180                       Wed May 26 14:11   still logged in
derk     pts/179                       Wed May 26 14:07 - 14:25  (00:18)
derk     pts/178                       Wed May 26 14:07   still logged in
derk     :1                            Wed May 26 14:07   still logged in
derk     pts/177                       Wed May 26 14:06 - 14:07  (00:00)
fez      pts/176                       Wed May 26 13:54 - 14:07  (00:12)
..snip
chris    pts/144                       Tue May 25 21:06 - 21:43  (00:36)
chris    zwift.zapvil zwift.zapville.o Tue May 25 21:06 - 21:43  (00:37)
derk     pts/143                       Tue May 25 21:05 - 21:21  (00:15)
derk     pts/142                       Tue May 25 20:19    gone - no logout
derk     :1                            Tue May 25 20:19 - 23:11  (02:52)

these are the 'gone - no logout' entries
some of these orphans show in the who  command

w1nd0w5  :0           May 25 16:33
derk     :1           May 26 14:07
fez      pts/18       May 18 14:06
chris    pts/44       May 19 21:19
derk     pts/109      May 24 18:44
derk     pts/114      May 25 06:57
w1nd0w5  pts/133      May 25 16:33
derk     pts/142      May 25 20:19
derk     pts/178      May 26 14:07
derk     pts/180      May 26 14:11
hannah   pts/188      May 26 15:50

where as the command
ls /dev/pts*
133  178  180

 shows only 3 'real' pts terminals active

where the users commnd gives .. when only two real users are logged in w1nd0w5 and derk the rest are relics ..

bash-2.05b$ users
chris derk derk derk derk derk derk fez hannah w1nd0w5 w1nd0w5

Somehow the parsing used in the who, users and other commands is less than reliable as dead terminal processes flagged by 'gone - no logout' should not show-up in the who or users listings even though they should show in 'last' as expected ..


Comment 6 Derk W te Bokkel 2004-05-26 17:21:44 UTC
opps forgot my utmp listing as well .. also could be adjusted as the relics show here too ..

bash-2.05b$ utmp
RUN_LVL       20019 /dev/~     runlevel
LOGIN_PROCESS 11708 /dev/tty1  LOGIN
LOGIN_PROCESS 11709 /dev/tty2  LOGIN
LOGIN_PROCESS 11710 /dev/tty3  LOGIN
LOGIN_PROCESS 11711 /dev/tty4  LOGIN
LOGIN_PROCESS 11712 /dev/tty5  LOGIN
LOGIN_PROCESS 11713 /dev/tty6  LOGIN
USER_PROCESS   5697 /dev/:0    w1nd0w5
USER_PROCESS   8911 /dev/:1    derk
USER_PROCESS  27180 /dev/pts/18 fez
USER_PROCESS  28805 /dev/pts/44 chris
USER_PROCESS  11371 /dev/pts/109 derk
USER_PROCESS  20591 /dev/pts/114 derk
USER_PROCESS   5773 /dev/pts/133 w1nd0w5
USER_PROCESS  12161 /dev/pts/142 derk
USER_PROCESS   8991 /dev/pts/178 derk
USER_PROCESS   9200 /dev/pts/180 derk
USER_PROCESS  18429 /dev/pts/188 hannah
Comment 7 SpanKY gentoo-dev 2004-10-09 19:17:57 UTC
iirc, this could be an issue with older utempter ?
Comment 8 Donnie Berkholz (RETIRED) gentoo-dev 2004-10-10 00:06:17 UTC
Looks like a dup to me.

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