19 messages in net.sourceforge.lists.courier-usersRe: Infinite loop (WAS: Re: [courier-...
FromSent OnAttachments
Alexander LazicMar 28, 2001 9:49 am 
Sam VarshavchikMar 28, 2001 11:58 am 
Jason TuckerMar 28, 2001 12:26 pm 
Sam VarshavchikMar 28, 2001 1:32 pm 
Jason TuckerMar 28, 2001 1:41 pm 
Jason TuckerMar 28, 2001 2:22 pm 
Sam VarshavchikMar 28, 2001 3:02 pm 
Jason TuckerMar 28, 2001 7:02 pm 
Sam VarshavchikMar 28, 2001 8:08 pm 
Jason TuckerApr 2, 2001 11:33 am 
Sam VarshavchikApr 2, 2001 3:07 pm 
Jason TuckerApr 2, 2001 8:32 pm 
Sam VarshavchikApr 2, 2001 9:02 pm 
Jason TuckerApr 3, 2001 6:47 am 
Jason TuckerApr 3, 2001 9:24 am 
Jason TuckerApr 3, 2001 12:47 pm 
Sam VarshavchikApr 3, 2001 2:39 pm 
Sam VarshavchikApr 3, 2001 2:41 pm 
Jason TuckerApr 3, 2001 9:06 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Infinite loop (WAS: Re: [courier-users] Re: UID problem revisited)Actions...
From:Jason Tucker (jtuc@cyberfuse.com)
Date:Apr 3, 2001 9:24:22 am
List:net.sourceforge.lists.courier-users

On Tue, 3 Apr 2001, Jason Tucker wrote:

On Tue, 3 Apr 2001, Sam Varshavchik wrote:

Make sure that your bind is set up correctly.

I don't think there's a problem here. You are getting back a prompt 451 service unavailable, which is the expected response in this situation -- LDAP configuration failure. The high CPU utilization is probably due to a broken implementation of sigpause().

I'll take another look at the LDAP conf and see if anything is out of place. As for the sigpause() issue, it's Solaris 7 on Intel, so yeah... it could very well be broken. If I get some time, I may try build it on sparc and see if I have any better luck.

Yep... I had authldaprc and ldapaliasrc owned by courier:courier with mode 600, when it should have been 640. Alaises seem to be working now.

Still looking into the sigpause() problem. I hoped maybe Sun had some updated libc patches, but it looks like I'm relatively up to date. There is a recent kernel patch that includes some libc stuff, but the release notes don't reference any symptoms like what I'm seeing. Thinking about trying it out anyway, just in case...

__Jason