Bug 26431

Summary: init(8) manpage incoherent
Product: Documentation Reporter: dpelleg+bsd <dpelleg+bsd>
Component: Books & ArticlesAssignee: dd <dd>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description dpelleg+bsd 2001-04-08 13:00:02 UTC
The DIAGNOSTICS section includes the line:
getty repeating too quickly on port %s, sleeping  A process being started

Fix: 

Reword.
How-To-Repeat: man init
Comment 1 dima 2001-04-08 20:09:00 UTC
dpelleg+bsd@cs.cmu.edu writes:
> 
> >Number:         26431
> >Category:       docs
> >Synopsis:       init(8) manpage incoherent
>
> >Description:
> The DIAGNOSTICS section includes the line:
> getty repeating too quickly on port %s, sleeping  A process being started
> 
> >How-To-Repeat:
> man init
> >Fix:
> Reword.

Could you elaborate?  It seems perfectly coherent to me.

> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-doc" in the body of the message
>
Comment 2 dima 2001-04-10 02:04:23 UTC
Dan Pelleg <dpelleg+@cs.cmu.edu> writes:
>   getty repeating too quickly on port %s, sleeping  A process being started
> 
>  my brain threw a parsing exception. Where does the error message end, and
> where does the explanation start? Should I guess that from the fact that
> the "A" is capitalized and follows two spaces instead of just one? Yes, I

Okay, now I understand your concern.  Your original complaint of "it's
incoherent" wasn't of much help, you must understand.  Actually, the
reason I probably didn't notice this is because, on my screen, the
"getty repeating ... sleeping" part is in bold, so it was obvious
where the error message ended.  I can, however, understand that not
everyone reads man pages on terminals capable of such markup.

Per your suggestion, I just committed a change to -current which puts
newlines after both error messages and indents the paragraphs
following them.  I'll MFC it after the code freeze.

Thanks for the report,

					Dima Dorfman
					dima@unixfreak.org
Comment 3 dd freebsd_committer freebsd_triage 2001-04-10 02:04:34 UTC
State Changed
From-To: open->suspended

Fix as suggested by the originator committed to -current.  I'll MFC it 
after the code freeze. 


Comment 4 dd freebsd_committer freebsd_triage 2001-04-10 02:04:34 UTC
Responsible Changed
From-To: freebsd-doc->dd

I'll MFC it.
Comment 5 dd freebsd_committer freebsd_triage 2001-04-26 03:18:23 UTC
State Changed
From-To: suspended->closed

MFC'd.