On Fri, Sep 30, 2005 at 11:12:53AM +0200, Kiko Piris wrote:
> On 30/09/2005 at 00:04 -0700, Steve Langasek wrote:

> > The error message in question comes from a PAM_ABORT return from the
> > Linux-PAM library, which has also just been upgraded in unstable; and I see
> > that you're running the newest version.  However, this error is not
> > reproducible here, or on the systems of most other users, so I'll need
> > information about the contents of your /etc/pam.d/ configuration in order to
> > debug it.

> I have a system (sid dist-upgraded today) where I get this error (with
> cron):

> | Sep 30 10:30:01 bacterio CRON[19683]: (pam_unix) session opened for user 
> root by (uid=0)
> | Sep 30 10:30:01 bacterio CRON[19683]: Critical error - immediate abort

> On my desktop (also sid dist-upgraded today). Cron works perfectly.

> Attached is a tarball of /etc/pam.d of the failing system.

The PAM config itself looks fine.  Can you please also forward the contents
of your /etc/security/limits.conf?

> Installing libpam0g=0.79-1 libpam-modules=0.79-1 libpam-runtime=0.79-1
> makes the error disapear.

So you mean that this error only occurs with 0.79-2, *not* with 0.79-1?

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to