Re: cron + ldap = disaster?
>>>>> "Smith" == Brian Smith <firstname.lastname@example.org> writes:
Smith> Natxo Asenjo wrote:
>> I have successfully deployed a single sign on solution with
>> openldap, it works great. But, there is a little problem with
>> cron. Everytime one of the users' or system's crontab changes,
>> cron stops working. The number of cron processes skyrockets
>> (within minutes you see it going from 1 to hundreds) and the
>> overall response of the server is badly hit.
Smith> We use openldap with libnss-ldap and pam-ldap and do not
Smith> have this problem with cron jobs, servers are running woody
Smith> and sarge without problems. If you are on woody still,
Smith> check out the openldap and libnss from backports.org.
I'm not sure whether this is related but here's my contribution :)
I've experienced at-process explosions when /var partition was
accidentally filled (because of stupid apache log
configuration). Presumambly atd doesn't like to not being able to
write to /var -partition. Are You sure there's nothing fishy going on
with Your /var/spool/cron?
puh. (09) 1734 3236