Bug 119093

Summary: Ordering dependancy in installing laus and pam rpms
Product: Red Hat Enterprise Linux 3 Reporter: Suzanne Hillman <shillman>
Component: lausAssignee: Charlie Bennett <ccb>
Status: CLOSED WORKSFORME QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: srevivo
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-04-12 19:06:24 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 Suzanne Hillman 2004-03-24 22:26:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)
Gecko/20030225

Description of problem:
When installing laus and the pam rpm, it is currently set up such that
you must install pam _then_ laus, in order for things to work
correctly. There really should not be any such dependancy, _or_ it
should not be possible to install them in the wrong order.

Version-Release number of selected component (if applicable):
laus-0.1-48RHEL3, pam-0.75-54

How reproducible:
Didn't try

Steps to Reproduce:
1. Install laus
2. Install pam
3. Log in, and check if there was a laus log from pam, saying you
logged in. There will not be
    

Actual Results:  No message from pam in the laus log, about a login.

Expected Results:  There should be a message.

Additional info:

Comment 1 Charlie Bennett 2004-04-12 19:06:24 UTC
pam is dependent on laus.  The issues we were seeing that seemed to
indicate an ordering problem are covered by manual actions which must
be taken to configure PAM for support auditing.  These actions will be
documented in the certification guide.