On 10 Jul 1999 k@??? wrote:
> It turned out that the damage limitation in dbfn_read_with_length() in
> the file dbfn.c needs an improvement. The idea to log the event is OK,
> but it has the potential to do some serious damage in turn. In my case
> it happened that some calling process seemed to retry the access
> immediately which lead to 5000 lines per second added to both mainlog
> and paniclog. You can imagine, this filled the disk rather quickly.
> Logfiles available on request.
Yes, I suppose if you have a busy system with lots of messages to some
domain that is provoking this error, you would get lots of retries
happening.
> The cure I suggest is to add a sleep 1 there. As it's a "damage
> limitation function" we need not be concerned about speed here and
> reducing the speed of diskspace-grabbing by a factor of 5000 isn't too
> bad.
That certainly seems a harmless enough precaution.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
