Bug#308904: Related to a lib!?
reassign 308904 libpam-ldap thanks Hi Richard, Steve Greenland wrote: On 16-May-05, 10:55 (CDT), Klaus Ethgen kl...@ethgen.de wrote: There's really nothing cron can do about this. Strange. But why do cron die or block? And why do I have this problem only the last few weeks and not bevore? I can't tell you. But cron only uses PAM. How is cron supposed to know what PAM is doing? PAM is the tool making ldap calls, and needs to deal with ldap specific problems. Cron cannot. This never got reassigned to libpam-ldap, I suspect because the cron package was changing Maintainers right around that time. This may or may not be related to #206948, which I will be reassigning to libnss-ldap shortly. Regards, Christian signature.asc Description: OpenPGP digital signature
Bug#308904: Related to a lib!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Am Sa den 14. Mai 2005 um 15:39 schrieb Steve Greenland: Ah, you've hit bug 206948, or a variant thereof. Trying using nscd. Hmm... might be. I have to say that I thought to this bug too bevore. But in this Report cron dies completely and on my system cron never die. But I think the bug might be near this. To nscd, I just did run into many troubles when using nscd in the past so I'm not hapy with this piece of software. :-( Also I think that nscd is only for environments where the server might be not able to serv all clients. But I have a environment with one server, one or two clients and nine users. So this is very minimalistic. There's really nothing cron can do about this. Strange. But why do cron die or block? And why do I have this problem only the last few weeks and not bevore? Gruß Klaus - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen [EMAIL PROTECTED] Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iQEVAwUBQojCj5+OKpjRpO3lAQKfBQgAibJwoxzAIGEqVl+k/IJDJvQk/ZxNKi2P ACP1Rv+khHxckTKIxJqZWbQq8k3Ld9joStgMjVYQXsSo/Az9cb0ggjbdvCQfTjH+ npH8K4eGigva5Q6zXdYIlxxyCPuib4ve30eAxH5eEXuX1T6Mna/TLthHVRGET77O TD7Xgcpe/vk6bO+BTy99GSeITc9r3AJn95ckH7mbbn7X0s7f+hAiGYzvI/CBVrW5 xlCzWSVBW1PPzz847VmQeaLzXEDUgDzwPFqBbR3B3R+EfJQ1QPD/9BxKZAKM+hLS 3+AdtWPzkpUl1giWvu46S+bxKCWT3TUTPOOnyigPKfEnpJR6xBCIXw== =0Ppf -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308904: Related to a lib!?
On 16-May-05, 10:55 (CDT), Klaus Ethgen [EMAIL PROTECTED] wrote: There's really nothing cron can do about this. Strange. But why do cron die or block? And why do I have this problem only the last few weeks and not bevore? I can't tell you. But cron only uses PAM. How is cron supposed to know what PAM is doing? PAM is the tool making ldap calls, and needs to deal with ldap specific problems. Cron cannot. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308904: Related to a lib!?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hoi, I did many debugging now. I was not able to find the problem in concrete but this seams related to the libldap. The subsubprocess of cron is blocking while select() to a connection to the ldap server. However. it seems to be a bug only triggered in the combination cron and remote ldap server. Also it seems to be that if I strace the cron the problem will go away. So this is some kind of Heisenbug. Gruß Klaus - -- Klaus Ethgenhttp://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen [EMAIL PROTECTED] Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iQEVAwUBQoWnF5+OKpjRpO3lAQIpawf9FEopNlEhAhTj9O0GG677XrgHNJ1FJg1d 0Vkti+MroyfaGMlN3Q30L26lK7XWqus2NqZPE6fMY7aT4NZ4gKSjdM1OgEWBS51+ /1bIXBSaGrhTnwaOqyfvwKCS2mgHt0ztxcUqYgcwDPOOUYXRRob22uKNVGQnqFuY JihK2+kveho8pjxSHpX2aJdLfchxZQeD8MTEH82Qwm7Qx3dQBtj+aGSFoCQ9/tEx 173UXIxyPy5a2GPLr5ImmQV3v0KrVAqIGJN2cvMaUOH2luXDQkBZj4uenMgyq8nb zgXotZpeTww8yUacj5i971vMOkHn6Pi1qwKRz2IpM/5ggc7fRd9Zyg== =VqwG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308904: Related to a lib!?
On 14-May-05, 02:22 (CDT), Klaus Ethgen [EMAIL PROTECTED] wrote: Hoi, I did many debugging now. I was not able to find the problem in concrete but this seams related to the libldap. The subsubprocess of cron is blocking while select() to a connection to the ldap server. However. it seems to be a bug only triggered in the combination cron and remote ldap server. Also it seems to be that if I strace the cron the problem will go away. So this is some kind of Heisenbug. Ah, you've hit bug 206948, or a variant thereof. Trying using nscd. There's really nothing cron can do about this. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
