On Tue, May 10, 2011 at 01:01:24PM -0400, Chris Hoogendyk wrote:
>
>
> On 5/10/11 11:44 AM, McGraw, Robert P wrote:
> >Has anyone figured a way to get the Amanda man pages to work with Solaris?
> >
> >I use the web man pages, but it would be nice to have them local some times.
>
> Just to clarify that -- they "seem to work" (i.e. you can do `man
> amanda` and you get the man8 page for Amanda from
> /usr/local/man/man8), but the formatting notation isn't totally
> consistent with what is expected for man on Solaris. That results in
> some things not displaying correctly and the man page just cutting
> off in the middle of a sentence.
>
> So, for example, on an older version of Amanda on Solaris 10, the man page
> finishes up with:
>
> .amandahosts
> This is essentially the same as authentication except a
> different file, with almost the same format, is used.
> This is the default mechanism built into Amanda.
>
> The format of the
>
> SunOS 5.10 Last change: 02/07/2007 9
>
>
> ("Amanda" is underlined in that.)
>
> There is a critical word missing (it should say "same as .rhost
> authentication"), and it just cuts off without finishing the rest of
> the man page. The contents of the amanda.8 file at that point is:
>
> \&.amandahosts
> .RS 4
> This is essentially the same as
> \fB.rhosts\fR
> authentication except a different file, with almost the same
> format, is used. This is the default mechanism built into
> \fIAmanda\fR.
> .sp
> The format of the
> \fI.amandahosts\fR
> file is:
> .sp
> \fIhostname\fR
> [
> \fIusername\fR
> [
> \fIservice\fR
> ]*]
> .sp
>
>
> That's just an example. I have a recollection of manually editing
> and fixing man page files in the past, but haven't done that
> recently.
That looks like the period of ".rhosts" (and the last ".amandahosts")
is being interpreted as the control character to execute a macro
instead of plain text. As no macro named "rhosts" is defined :-)
the line is ignored.
Two ways of fixing the source, join the "dot line" with the
preceeding line to give "... the same as \fB.rhosts\fR" or put
a "\&" in front of the "dot line" as shown on the first line
above ("\&.amandahosts"). The "\&" is like a backslash on the
shell command line saying the following special character is
not special.
A third fix would be to use the macros ".B" and ".I":
.B .rhosts
.I .amandahosts
>
> In reply to Jon LaBadie's email,
>
> nroff -man amanda.8
> groff -man -T ascii amanda.8
>
> both return the same result as just doing `man amanda`.
Not having other info about the problem I thought that
location of the manpages was a possibility.
--
Jon H. LaBadie [email protected]
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
