On Tue, 27 Apr 2004, Joel wrote:I don't think that Binc is the correct place for this features: it should be in supervise. This is akin to adding code to Binc to work around client bugs.Gah, there are down files in the log directories. How did I not notice
that before? I knew I was doing something stupid... Oh well, at least I
learned another thing about daemontools today.
I got the log services started. Does this sound like something that
could have caused my earlier problems (binc stops responding after a while)?
Yes, and it's got me thinking about adding some log timeout warning feature in 1.3 to handle this problem. It's happened before, and it's not just Binc IMAP that stops; all services that log to multilog stop if multilog isn't doing its logging.
Furthermore, you have removed the "down" files from the distribution and the troubleshooting pages do a pretty good job of identifying this problem (although I am going to go make some improvements).
Henry
The lock-up is fine, IMHO, or else log data could be lost. The problem is that the admin doesn't get to know about it. :-)
Andy :-)
-- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
-- Henry Baragar Principal, Technical Architecture 416-453-5626 Instantiated Software Inc. http://www.instantiated.ca
