Date: Fri, 14 Dec 2001 03:40:18 -0800 (PST) From: Rocco Lucia <rlucia@iscanet.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/32828: w incorrectly handles stale utmp slots with jail Message-ID: <200112141140.fBEBeIx24089@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 32828
>Category: bin
>Synopsis: w incorrectly handles stale utmp slots with jail
>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 Dec 14 03:50:07 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Rocco Lucia
>Release: 4.4
>Organization:
>Environment:
FreeBSD signonssh.cs.tin.it 4.4-STABLE FreeBSD 4.4-STABLE #1: Mon Dec 3 10:11:14 CET 2001 root@signonssh.cs.tin.it:/usr/obj/usr/src/sys/SIGNONSSH i386
>Description:
While using jail, w command on host machine erroneously handles 'current process' for a stale utmp slot.
It will show as 'current process' that one who is actually run in the jail and whose controlling terminal line is the same as it was used in the host machine.
>How-To-Repeat:
1. log into the jail and allocate different ttys (screen could help)
2. log into the host machine and have the process killed or disconnected (create a stale utmp record)
Manage steps 1 and 2 so that you have at least a session on host machine and a session in the prison that share same tty name (/dev/ttyp1 on host, and ${JAIL}/dev/ttyp1 in the prison).
3. now issue the w command on the host system and you'll see the 'current process' for the stale utmp record being a process running in the jail but that has same tty (though on two different environments).
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112141140.fBEBeIx24089>