Bug 7417
Summary: | No information re: hostname and user associated with stdin | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Scott Gibson <wsgibson> |
Component: | sh-utils | Assignee: | bero |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | wsgibson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-04 15:19:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Scott Gibson
1999-11-29 20:45:29 UTC
The basic problem is that 'who' has the -m option at all. utmp entries are for login sessions, not shell prompts, so there is no direct correlation between a particular pty and a particular session. The -m option mostly remains for historical reasons - in the "old days", they didn't have to worry about things such as logins via gdm etc. :) The basic problem is that 'who' has the -m option at all. utmp entries are for login sessions, not shell prompts, so there is no direct correlation between a particular pty and a particular session. The -m option mostly remains for historical reasons - in the "old days", they didn't have to worry about things such as logins via gdm etc. :) |