Problems with Cyrus IMAP 2.1.13

[Rob Siemborski]

On Fri, 6 Jun 2003, Gareth Bult wrote:

> >Jun  6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor
> 0: Socket is not connected
>
> Means your client has dropped out 'uncleanly'.

Its a harmless log message, and if you're logging at LOG_DEBUG you should
expect to see a lot of harmless log messages.

In the next version of cyrus we've turned off logging for "socket is not
connected" totally.

> Shut down Cyrus and let incoming queue and users cry.
> ctl_cyrusdb -r
> reconstruct
> Start Cyrus back up.

You shouldn't ever need to reconstruct unless a mailbox is corrupted (And
that can be done live).  ctl_cyrusdb -r should *always* be run becfore
cyrus starts (it should be in the START section of master.conf).

> Statements made are at all times subject to Frontier's Terms and
> Conditions of Business, which are available upon request.

I'm not sure what these conditions are, but disclaimers like this
generally can make it hard to take posts to public mailing in any serious
way (for example, if the disclaimer is that the contents of the message on
a public list is "confidential" what does that mean?)

-Rob


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper