Sorry for the misdirected finger pointing earlier. Touching
/etc/environment, without making changes in /etc/pam.d/ (ie pam_env still
being called) now allows logins via ssh, and cron jobs are starting to run
again
On Fri, 30 Sep 2005, Kiko Piris wrote:
On 30/09/2005 at 03:51 -0700, Steve Langasek wrote:
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?
You're right, it goes away commenting out pam_env.
If that does fix it, please post your /etc/environment as well.
It didn't exist, just touched it and the error went away.
Thanks,
Thank you, indeed.
--
Kiko
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
