Randy Barlow <[EMAIL PROTECTED]> writes:

> [EMAIL PROTECTED] wrote:
>> It never really says where the code it presents is to be found but I'm
>> guessing it would be the files under /etc/security
>> all those files are commented out except  namespace.init that has this
>> line uncommented:
>>    exit 0
>> Maybe something needs to be uncommented in one of them.
>
> /etc/security isn't the only place to look.  I use PAM on my mail server
> and IMAP server, and I had to change some files in there that used the
> old way.  Do you have a mail server that uses PAM?  Do you have a web
> server that uses PAM?  Any other services?

Randy, I responded to this quite a while ago but do not see that
response here.. Looking locally I don't see a saved copy so I must
have closed the program I was writing from another desktop or
something. 

Thanks for your input but I don't think that was the problem.
I do run a local webserver (home lan) and run sendmail which isn't set
up as a server though.

Further, the output of  `equery files pam' only shows two places where
configs might be.  The update site referred to in the error message
doesn't tell where to look or if so I missed it

Anyway a grep in /etc/pam.d for any of the modules mentioned in the
error shows nothing but a few commented lines all in /etc/pam.d/login.
 
  grep -r 'pwdb\|radius\|timestamp\|console' 

# If you want to enable pam_console, uncomment the following line
# and read carefully README.pam_console in /usr/share/doc/pam*
# session    optional   pam_console.so

Now the good part:
`emerge -vC pam' followed by a continuing of 
`emerge -vuDPN world'

Seems to have gotten over the pam hurdle.

-- 
[EMAIL PROTECTED] mailing list

Reply via email to