Bug 55

Summary:	rsh problems with utmp
Product:	[Retired] Red Hat Linux	Reporter:	cadams
Component:	rsh	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-03-26 15:35:26 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 cadams 1998-11-12 17:23:47 UTC

If rsh doesn't enter a LOGIN entry in the utmp file, login
gets confused and adds a new entry at the end (even if an
entry for the tty already exists).  This causes the utmp
file to keep growing as long as the system is up.  A utmp
file over 1MB makes "who", "w", and other such programs slow
to a crawl on an active server.

I will send a patch for rsh that makes it create an entry
once I get a bug ID.

Comment 1 Derek Tattersall 1998-11-19 17:35:59 UTC

See patch in attached email.

Comment 2 Jeff Johnson 1999-02-18 15:54:59 UTC

This patch has been added to the OpenBSD rsh sources in Raw Hide.
This is an intermediate solution until a PAM module is written
that will manage utmp entries. Thanks for the patch.

Comment 3 Jeff Johnson 1999-03-26 15:35:59 UTC

And, finally, a better fix (to find utmp entry based on tty slot)
has been put into login.c that makes it unnecessary to create the
utmp entry before exec'ing login. Thanks for pointing this out.

Fix is in util-linux-2.9o-6.