[follow-up] ctlinnd reload history <reason> kills innd

[William F. Maton]

On Wed, 6 Mar 2002, Jeffrey M. Vinocur wrote:

> First thing is that I don't trust that error message -- I'm going to go
> through and fix up the history code to set errno before returning, since
> we seem to make use of it.  (Currently the check for a null pointer just
> returns false without setting errno.)
>
> When does the above occur?  After a reload?

Immediately after reloading history, and keeps happening, with the
following two messages:

Mar  6 14:44:12 crc-news innd: SERVER throttle Interrupted system call
writing history write file -- throttling
Mar  6 14:45:34 crc-news innd: SERVER throttle Interrupted system call
writing history remember file -- throttling

The former message appears far more frequently than the latter....

wfms