Re: Experiment to test TCP keepalive for pop3d proxies

Since you mention it... I took a look at a random frontend, and found 27 or 33 pop processes from two days ago. I used gdb to get stack traces from 3 samples, all looked like this: (gdb) where #0 0x008007a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x008d6ff3 in __read_nocancel ()

Experiment to test TCP keepalive for pop3d proxies

Ever since I can remember, our Cyrus installation had a problem with pop3d processes accumulating on the murder front end server. This didn't happen with imapd processes or with pop3d on the back end. A couple of weeks ago, I counted 423 pop3d processes on the front end but only 37 on the back en

unsubscribe

Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: ldap groups and ptloader

On 27 May 2010, at 06:38, Duncan Gibb wrote: > Yes. It would be nice when someone has time to make the configuration > of pts_ldap more similar to other things likely to be using the same > data (eg pam/nss/samba as well as saslauthd). Comments on: https://bugzilla.andrew.cmu.edu/show_bu

Re: imapd, TLS and CRLs

Can you submit this to the Cyrus Bugzilla, please. :wes On 27 May 2010, at 13:04, Stacy Millions wrote: > I have been working on deploying an imap server using EXTERNAL+TLS > authentication. Everything is working fine and then I discover that > there is no support CRLs in imapd; from my point

imapd, TLS and CRLs

I have been working on deploying an imap server using EXTERNAL+TLS authentication. Everything is working fine and then I discover that there is no support CRLs in imapd; from my point of view this is a Bad Thing(tm). I searched the mailing list and found a discussion of this in 2005/02 with t

cyrus replication and RENAME problem

Hi list, we have a cyrus murder cluster with two frontends,two backends and two replication servers, all running cyrus version 2.3.14. Each backend has two partitions. The two backends are replicated to the replication servers using the cyrus replication mechanism (sync_client -r). The replication

Re: ldap groups and ptloader

Hi Duncan, > JDG> My groups are "posixGroup" with the uid's of the members listed > JDG> in the memberUid attribute, the group name is listed in the cn > JDG> attribute: > > If you add > > ldap_member_attribute: cn > > to your config, it should work. Certainly something very similar works > on

Re: ldap groups and ptloader

Jos De Graeve wrote: JDG> I use saslauthd to auth against ldap (bind auth) and I am trying JDG> to use ptloader to fetch group information from LDAP so that group JDG> based ACL's can be used for shared folders. We have several similar systems in production. JDG> If I look with ptdump each user

ldap groups and ptloader

Dear list, I use saslauthd to auth against ldap (bind auth) and I am trying to use ptloader to fetch group information from LDAP so that group based ACL's can be used for shared folders. The ldap auth works fine, but the group information gets screwed up somewhere. With tcpdump I see my director