Bug 134655

Summary:	pam_env requires /etc/environment to exist
Product:	Red Hat Enterprise Linux 4	Reporter:	David Juran <djuran>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED NEXTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	goeran, hongjiu.lu, shillman
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:	2004-10-06 03:51:20 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:	134551

Description David Juran 2004-10-05 13:55:12 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)
Gecko/20040803

Description of problem:
pam_env, which is by default called from system_auth, requires the
file /etc/environment to exist. This file however is not part of the
distribution. Therefor it is e.g. not possible to do rsh to the system.

Version-Release number of selected component (if applicable):
pam-0.77-56

How reproducible:
Always

Steps to Reproduce:
1. rsh ams
Critical error - immediate abort
rlogin: connection closed.


Additional info:

Comment 1 Suzanne Hillman 2004-10-05 18:16:12 UTC

Can you give a bit more information on how you determined that
/etc/enviroment was needed by pam_env? Does this show up as an error
when it tried to run?

Comment 2 David Juran 2004-10-05 18:54:55 UTC

A quick look in the sourcecode for pam gave me the hint that this was
the case. And then
touch /etc/environment
remedied the problem (-:

Comment 4 Bill Nottingham 2004-10-06 03:51:20 UTC

This is fixed in current setup packages.

Comment 6 Tomas Mraz 2004-10-08 07:53:48 UTC

*** Bug 133564 has been marked as a duplicate of this bug. ***