-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said...
> Symptoms: > > 1) exim is churning away with 20-40% cpu usage and load between 1 and 2 > on an otherwise unladen machine > > 2) my exim logs are growing huge; tail -f shows several new entriers > per second saying "message frozen" [...] > Anyone know what's going on? Frozen messages are those that could not be delivered and require human intervention to get them out of the queue. Exim will very easily to what you describe if you have a massive number (on the order of tens of thousands) of frozen messages in the queue. The next step is to find out why those messages froze, and fix the problem. For future reference, you can run "/usr/sbin/exiwhat" as root to find out what Exim is doing. - -- - ---------------------------------------------------------------------- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine iD8DBQE7PLn4/ZTSZFDeHPwRAgAcAKCSSh2hkzyzRF5qP7IxXEHlp/4XywCeKUWM Tc6BLlybVT+2AqbC7XQTSZs= =7HIQ -----END PGP SIGNATURE-----
