Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 125589
Summary: | sshd does not update /var/run/utmp when allocated pty > 999 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | R Deepak <rdeepak> | ||||
Component: | openssh | Assignee: | Nalin Dahyabhai <nalin> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 2 | CC: | adrian, barryn, moneta.mace, rdeepak, wtogami | ||||
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: | 2004-11-01 22:54:38 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 123268, 125270 | ||||||
Attachments: |
|
Description
R Deepak
2004-06-09 04:24:00 UTC
As a side comment from the previously referenced bug, if an active openssh session (i.e. gnome-terminal window) is running in X, and X is is killed, /var/run/utmp does not seem to be updated correctly either. Steps to Reproduce: 1. After a fresh login into X using gnome, open a terminal window: elisha: ~> finger Login Name Tty Idle Login Time Office Office Phone kriehn Gregory Kriehn *:0 Jun 9 10:41 kriehn Gregory Kriehn pts/1 Jun 9 10:41 (:0.0) elisha: ~> w 10:43:26 up 2 min, 2 users, load average: 0.86, 0.78, 0.33 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT kriehn :0 - 10:41 ?xdm? 24.67s 0.06s -/bin/tcsh -c / kriehn pts/1 :0.0 10:41 0.00s 0.07s 0.00s w 2. Leave the terminal window open and kill X with Ctrl-Alt-Backspace. 3. Next, log back into gnome after X restarts and open a new openssh session: elisha: ~> finger Login Name Tty Idle Login Time Office Office Phone kriehn Gregory Kriehn *:0 Jun 9 10:46 kriehn Gregory Kriehn pts/1 54d Jun 9 10:41 (:0.0) kriehn Gregory Kriehn pts/2 Jun 9 10:46 (:0.0) elisha: ~> finger Login Name Tty Idle Login Time Office Office Phone kriehn Gregory Kriehn *:0 Jun 9 10:46 kriehn Gregory Kriehn pts/1 120d Jun 9 10:41 (:0.0) kriehn Gregory Kriehn pts/2 Jun 9 10:46 (:0.0) elisha: ~> w 10:46:51 up 6 min, 3 users, load average: 0.53, 0.57, 0.32 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT kriehn :0 - 10:46 ?xdm? 19.26s 0.06s -/bin/tcsh -c / kriehn pts/2 :0.0 10:46 0.00s 1.61s 0.00s w Notice the random idle times generated resulting from the stale openssh session on pts/1. Created attachment 101019 [details]
sample output..
I built rpms with updated openssh 3.8.1p1 modified to use LINFO_LINESIZE and this solves the first issue. There is no problem when allocated pts is greater that 999. There is one issue though finger displays only 3 digit pts numbers. So, pts/1000 is displayed as pts/100. 'w' works fine. Look at attachment for sample output. I can confirm this bug. I have the same problem. $ w 11:58:33 up 21 days, 1:52, 417 users, load average: 0.49, 1.00, 1.34 ^^^^^^^^^^ with only ten users logged in. Looks fixed with current rpm packages. I have installed openssh from FC3test2 on a FC2 system. Currently the highest used pts is 721, but in some days it will reach 1000. I will then add an additional comment if this is fixed for me or not. I can confirm that this error is fixed on my system (FC2). openssh-clients-3.9p1-3 openssh-3.9p1-3 openssh-server-3.9p1-3 ptys higher than 1000 are used and users logging out are correctly logged without any error messages in any logs. commands like w, who, finger and last work as expected (logged out users stay no longer logged-in) |