On Fri, Sep 30, 2005 at 12:39:56PM +0200, Kiko Piris wrote:
> On 30/09/2005 at 02:40 -0700, Steve Langasek wrote:

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

> Attached. It's empty (only comments).

Hrm.

> > > 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?

> That's correct.

Ok, the only module that's used by your cron config which actually changed
between 0.79-1 and 0.79-2 was pam_env.  Could you please upgrade to 0.79-2
again, confirm that you're still seeing the bug, then comment out pam_env in
/etc/pam.d/cron  to see if the problem goes away?

If that does fix it, please post your /etc/environment as well.

If it doesn't fix it, can you also try commenting out pam_limits, just for
kicks?

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