Thought I'd mention an odd problem with idled which I've worked around so that it gets into the list archive. Running 2.3.16, the master starts idled without error. However, all of the services initially started by master would fail to contact idled and give the following error: imap[23494]: error sending to idled: 3 Inspection of the source indicates that 3 is the NOOP operation, sent during the initial ping over the socket to ensure that idled was available. The socket exists and permissions are OK. A search of the list archives turned up no relevant hits, except for one person seeing the same error who does not seem to have received a reply. http://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2006-November/000802.html Services started by the master later would connect to idled without issue. Adding another START item after idled in cyrus.conf (in this case, syncclient) caused the problem to go away. It looks as if master starts the services before idled is ready to accept connections, and adding another service to the START section delays things just enough. This system is pretty fast (dual socket quad core Nehalem with 48GB of RAM) but I'm sure others have run on fancier hardware so I'm not sure what's up. - J< ---- 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
