Bug#1751: corrupt man page for dc

["Susan G. Kleinmann" <sgk@soos.tiac.net>]

I should have noted that:
-- I was also using man-2.3.10-2, and
-- when I ran mandb, I got no other error messages than the one
   associated with dc.

Other than the message about dc, running mandb -c had (for me) the
desired beneficial effect of eliminating an error message I kept
getting from 'apropos' after I'd manually placed some pages in
/usr/local/man/manl.

Susan
===================================================

> "Susan G. Kleinmann" <sgk@soos.tiac.net> said:
>
> > When running the command mandb -c, I got the message:
> > Processing manual pages under /usr/man...
> > mandb: warning: /usr/man/man1/dc.1: whatis parse for dc(1) failed
>
> I'm going to try to reassign this bug report from dc to man.
> When I tried to reproduce it on my system, I saw the following:
>

Bill Mitchell ,mitchell@mdd.comm.mot.com> said:
> Script started on Tue Oct 24 07:19:51 1995
> # mandb -c
> Processing manual pages under /usr/man...
> mandb: warning: /usr/man/man8/in.smtpd.8: whatis parse for in.smtpd(8) failed
> mandb: warning: /usr/man/man8/mailq.8: whatis parse for mailq(8) failed
> mandb: warning: /usr/man/man8/sendmail.8: whatis parse for sendmail(8) failed
> mandb: warning: /usr/man/man8/runq.8: whatis parse for runq(8) failed
> mandb: warning: /usr/man/man8/rmail.8: whatis parse for rmail(8) failed
> mandb: warning: /usr/man/man8/rsmtp.8: whatis parse for rsmtp(8) failed
> mandb: warning: /usr/man/man1/uupath.1: whatis parse for uupath(1) failed
> mandb: warning: /usr/man/man1/dc.1: whatis parse for dc(1) failed
> Checking for stray cats under /usr/man...
> Checking for stray cats under /var/catman...
> 9 man subdirectories contained newer manual pages.
> 1196 manual pages and 0 stray cats were added.
> #
> Script done on Tue Oct 24 07:20:07 1995
>
> This was with man-2.3.10-2.
>
>
===================================================