Comment # 8 on bug 1155879 from Ulrich Windl

(In reply to Dr. Werner Fink from comment #6)
> The line which may cause this is:
> 
>    find $mp -follow -newer $db | read -t 1 line
> 
> that is somehow the read builtin of the bash dies before find is finished
> here.

IMHO read does not DIE, but it may run into the specified TIMEOUT of one second
when the load is a bit high. Effectively the code was not testing whether find
returned something, but it timed out find via broken pipe, causing a write
error.

(In reply to Ulrich Windl from comment #0)
> Nov 05 09:52:59 pc do_mandb[2568]: find: ���standard output���: Broken pipe
> Nov 05 09:52:59 pc do_mandb[2568]: find: write error


(In reply to Dr. Werner Fink from comment #6)
> Nevertheless as this does not hurt I'll decrease severity
(I wonder why this is priority "enhancement")
Of course not updating the mandb is not serious, but seen from the perspective
of the code it was just wrong (and thus is a bug).