Bug 58057 – man named.conf produces mdoc warnings

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 58057 - man named.conf produces mdoc warnings

Summary:	man named.conf produces mdoc warnings

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	man-pages (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Eido Inoue
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-01-07 08:33 EST by Dave Reed
Modified:	2007-04-18 12:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-08-20 14:43:08 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Dave Reed 2002-01-07 08:33:21 EST

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; SunOS 5.7 sun4u)

Description of problem:
man named.conf produces a number of lines like the following:
mdoc warning: Empty input line #436

man resolv.conf produces one line like that

These are the only two man pages for which I noticed the problem.

I don't know whether this is a problem with man, the man-pages, or possibly
groff.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. man named.conf
2. man resolv.conf

	

Actual Results:  lots of extra lines like:
mdoc warning: Empty input line #436

Expected Results:  I don't expect to see those lines, just the man page.

Additional info:

Comment 1 Trond Eivind Glomsrxd 2002-01-14 12:35:41 EST

Completely harmless, should probably be fixed.

Note You need to log in before you can comment on or make changes to this bug.