misc/53293: Sticky user on 5.1 (who/su)
Jimmy Selgen
jsn at chantry.devlix.dk
Fri Jun 13 12:40:22 PDT 2003
>Number: 53293
>Category: misc
>Synopsis: Sticky user on 5.1 (who/su)
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Jun 13 12:40:19 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator: Jimmy Selgen
>Release: FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
System: FreeBSD some.where.dk 5.1-RELEASE FreeBSD 5.1-RELEASE #16: Tue Jun 10 11:24:37 CEST 2003 root at some.where.dk:/usr/obj/usr/src/sys/KCONF i386
>Description:
Hi.
I tried posting this to the freebsd-current list, but so far i've recieved no answers :(
This might be a common error/misconfiguration, but i've been unable to
locate it in the archives..
Using 5.1-RELEASE (upgraded from 5.0 through buildkernel/buildworld to RELENG_5_1).
I'm seeing the following "strangeness"
I login as a normal user, run who .. shows my own username as logged in.
su to another user, logout (back to my own uid), run who, and "su'ed" user
is still listed for my session.
Here's a little "screenshot" (names have been changed to protect the
innocent :* )
-bash-2.05b$ w
11:09PM up 2 days, 11:27, 2 users, load averages: 1.19, 1.17, 1.16
USER TTY FROM LOGIN@ IDLE WHAT
test1 p0 xxx.xx.x.xxx 11:09PM - w
-bash-2.05b$ su - test2
Password:
Last login: Thu Mar 6 18:39:11 from something.somewhere.
-su-2.05b$ w
11:09PM up 2 days, 11:27, 2 users, load averages: 1.24, 1.18, 1.17
USER TTY FROM LOGIN@ IDLE WHAT
test2 p0 - 11:09PM - w
-su-2.05b$ logout
-bash-2.05b$ w
11:09PM up 2 days, 11:27, 2 users, load averages: 1.22, 1.18, 1.17
USER TTY FROM LOGIN@ IDLE WHAT
test2 p0 - 11:09PM - w
-bash-2.05b$ who am i
test2 ttyp0 Jun 12 23:09
----
uname -a gives the following :
FreeBSD some.where.com 5.1-RELEASE FreeBSD 5.1-RELEASE #16: Tue Jun 10
11:24:37 CEST 2003 root at some.where.com:/usr/obj/usr/src/sys/KCONF
i386
I'm trying to do a build of 5.1-CURRENT to see if that'll solve the problem.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list