[Citadel Development] (no subject)

2006-04-04 Thread IGnatius T Foobar
There is a slight possibility that I may be getting a handle on some of the weird connectivity and performance problems with Citadel on FreeBSD. fleeb and others ... check your logs for the following message: client_write() failed: resource temporarily unavailable It

[Citadel Development] (no subject)

2006-04-04 Thread fleeb
Hmm... looking over my logs, I do not yet see something like that.

[Citadel Development] (no subject)

2006-04-04 Thread IGnatius T Foobar
Actually, the R in resource is capitalized. buzzwang sent me some sample messages, and I was able to use one of them to reliably produce a problem every single time -- a call to write() on the socket produced EAGAIN, which made the client barf. Presumably an IMAP client would do the

[Citadel Development] (no subject)

2006-04-04 Thread IGnatius T Foobar
ok ... WebCit doesn't have the same problem because the network listener is structured a little bit differently. In the Citadel server, we put in a call to fcntl() to set all master listening sockets to non-blocking, in order to deal with a rare situation in which select() told us about

[Citadel Development] (no subject)

2006-04-04 Thread IGnatius T Foobar
The IANA has assigned the following Private Enterprise Number to citadel.org (the Citadel groupware project): 25404 Please see the following for your assignment in the registry: http://www.iana.org/assignments/enterprise-numbers Ok, so