severity 686110 wishlist tags 686110 +wontfix thank you On Tue, Aug 28, 2012 at 7:46 PM, Jamie Thompson <bugs.deb...@jamie-thompson.co.uk> wrote: > Following a power failure my tls_sessions.db file became corrupted (UPS > is currently out of commission - anyway). When the server restarted, I > did not notice this fact and would not do so until my next logcheck > email (or an attempt to check my mail). Unfortunately, within a few > hours my logfiles ended up being full of cyrus's infinite unsuccessful > startup attempts, resulting in 6GB of logfiles, which so happened to > take my server down. > > Ideally Cyrus should try to recover the databases, if that fails, > delete the session-specific recreateable ones (i.e. tls_sessions.db) > and try again, and if it is still unable to start, stop trying as > without intervention it's just wasting electricity and disk space.
Well, ideally you should check your system, deamons and logs after a power failure. I don't think upstream would want to waste development cycles on something which can be easily circumvented by human operator. O. -- Ondřej Surý <ond...@sury.org> _______________________________________________ Pkg-Cyrus-imapd-Debian-devel mailing list Pkg-Cyrus-imapd-Debian-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel
