Sponsored Content
Full Discussion: man pages
Top Forums UNIX for Dummies Questions & Answers man pages Post 16347 by killerserv on Thursday 28th of February 2002 07:21:49 AM
Old 02-28-2002
For the man command to be able to find and display a man page, the man page has to be placed in the appropriate directory. The FILES section of man(1) lists these quite well:
Code:
    /usr/share/catman/u_man/cat[1,6]/*     user manual pages
    /usr/share/catman/a_man/cat[1,4,7]/*   system administrator manual pages
    /usr/share/catman/p_man/cat[2-5]/*     programmer manual pages
    /usr/share/catman/g_man/cat3/*         Graphics Library manual pages
    /usr/share/catman/local/cat[1-8lnop]/* local pre-formatted manual entries
    /usr/catman/local/man[1-8lnop]/*       local unformatted nroff(1) source
                                           manual entries
    /usr/share/man/*                       additional unformatted manual pages

** Man pages are also often placed in directories such as /usr/local/man. The characters at the end of the directory names are the section-numbers of the man pages. Man pages you have written will be unformatted so should be placed in the man[1-8lnop] directories as opposed to the cat directories.

Hope you get what you looking for.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Man pages

Hello , I just installed openssh in my system . I actually tried to man sshd but it says no entry , though there is a man directory in the installation which have the man pages for sshd . Can anyone tell me how should i install these man pages . DP (2 Replies)
Discussion started by: DPAI
2 Replies

2. UNIX for Dummies Questions & Answers

man pages

Hi folks, I want to know all the commands for which man pages are available. How do i get it? Cheers, Nisha (4 Replies)
Discussion started by: Nisha
4 Replies

3. UNIX for Dummies Questions & Answers

man pages

When reading man pages, I notice that sometimes commands are follwed by a number enclosed in parenthesis. such as: mkdir calls the mkdir(2) system call. What exactly does this mean? (4 Replies)
Discussion started by: dangral
4 Replies

4. Shell Programming and Scripting

how to best browse man pages?

guys...usually we simply browse the man pages with "man commandName" are there better ways to browse the man pages? i also see many underlined words in man pages...does they have some special signifigance like the one in html.. i.e can they be directly refered for complete reference? is... (5 Replies)
Discussion started by: RishiPahuja
5 Replies

5. AIX

man pages in AIX

Hi all. A friend of mine just recently gave me an old RISC 6000 machine to learn on for my AIX certification. I installed AIX 4.3.3 and everything seems to work fine, except there are no man pages. Is there a way to generate man pages on this machine? Thanks alot in advance. (5 Replies)
Discussion started by: dlynch912
5 Replies

6. Fedora

why do we have .1 extension in MAN PAGES?

Hello sir, I am using FEDORA 9. I wanted to know why do we have ".1" extension in the archives of man pages. I know we are giving format. I want to know the importance or purpose of this format. Can you please tell me :confused: (2 Replies)
Discussion started by: nsharath
2 Replies

7. Post Here to Contact Site Administrators and Moderators

Extended man pages

Hi, Any chance we could have an input pane in the forums that targets a man page and whose content is output to the bottom of the man page in this way forming extended man pages with additional know how? Thanks, Steve (9 Replies)
Discussion started by: spaesani
9 Replies

8. Solaris

man pages issue

hi all i have installed veritas storage foundation 5.1 in my sun blade 150 which running with sun solaris 5.10. Veritas commands manual pages are located in /opt/VRTS/man/man1m directory. But if i give "man vxassist" It says "no manual entry for vxassist". How to resolve this? (2 Replies)
Discussion started by: kingston
2 Replies

9. Solaris

MAN PAGES

Hi everyone, I have a small query, in solaris the man pages get displayed on half of the terminal , can i get a full terminal or full screen display ?:) (2 Replies)
Discussion started by: M.Choudhury
2 Replies

10. HP-UX

Looking for some man pages.

Can anyone supply me with the man pages for: omnidatalist omnibarlist omnisap.exe I prefer the source man pages in nroff format. A clue about the software bundles which supply these man pages is fine as well. OS: HP-UX TIA (11 Replies)
Discussion started by: sb008
11 Replies
catman(1M)						  System Administration Commands						catman(1M)

NAME
catman - create the formatted files for the reference manual SYNOPSIS
/usr/bin/catman [-c] [-n] [-p] [-t] [-w] [-M directory] [-T macro-package] [sections] DESCRIPTION
The catman utility creates the preformatted versions of the on-line manual from the nroff(1) or sgml(5) input files. This feature allows easy distribution of the preformatted manual pages among a group of associated machines (for example, with rdist(1)), since it makes the directories of preformatted manual pages self-contained and independent of the unformatted entries. catman also creates the windex database file in the directories specified by the MANPATH or the -M option. The windex database file is a three column list consisting of a keyword, the reference page that the keyword points to, and a line of text that describes the purpose of the utility or interface documented on the reference page. Each keyword is taken from the comma separated list of words on the NAME line before the `-' (dash). The reference page that the keyword points to is the first word on the NAME line. The text after the - on the NAME line is the descriptive text in the third column. The NAME line must be immediately preceded by the page heading line created by the .TH macro (see NOTES for required format). Each manual page is examined and those whose preformatted versions are missing or out of date are recreated. If any changes are made, cat- man recreates the windex database. If a manual page is a shadow page, that is, it sources another manual page for its contents, a symbolic link is made in the catx or fmtx directory to the appropriate preformatted manual page. Shadow files in an unformatted nroff source file are identified by the first line being of the form .so manx/yyy.x. Shadow files in the SGML sources are identified by the string SHADOW_PAGE. The file entity declared in the shadow file identifies the file to be sourced. OPTIONS
The following options are supported: -c Create unformatted nroff source files in the appropriate man subdirectories from the SGML sources. This option will overwrite any existing file in the man directory of the same name as the SGML file. -n Do not create (or recreate) the windex database. If the -n option is specified, the windex database is not created and the apropos, whatis, man -f, and man -k commands will fail. -p Print what would be done instead of doing it. -t Create troffed entries in the appropriate fmt subdirectories instead of nroffing into the cat subdirectories. -w Only create the windex database that is used by whatis(1) and the man(1) -f and -k options. No manual reformatting is done. -M directory Update manual pages located in the specified directory, (/usr/share/man by default). If the -M option is speci- fied, the directory argument must not contain a `,' (comma), since a comma is used to delineate section numbers. See man(1). -T macro-package Use macro-package in place of the standard manual page macros, ( man(5) by default). OPERANDS
The following operand is supported: sections If there is one parameter not starting with a `-', it is taken to be a space separated list of manual sections to be pro- cessed by catman. If this operand is specified, only the manual sections in the list will be processed. For example, catman 1 2 3 only updates manual sections 1, 2, and 3. If specific sections are not listed, all sections in the man directory specified by the environment variable MANPATH are processed. ENVIRONMENT VARIABLES
TROFF The name of the formatter to use when the -t flag is given. If not set, troff(1) is used. MANPATH A colon-separated list of directories that are processed by catman and man(1). Each directory can be followed by a comma- separated list of sections. If set, its value overrides /usr/share/man as the default directory search path, and the man.cf file as the default section search path. The -M and -s flags, in turn, override these values. FILES
/usr/share/man default manual directory location /usr/share/man/man*/*.* raw nroff input files /usr/share/man/sman*/*.* raw SGML input files /usr/share/man/cat*/*.* preformatted nroffed manual pages /usr/share/man/fmt*/*.* preformatted troffed manual pages /usr/share/man/windex table of contents and keyword database /usr/lib/makewhatis command script to make windex database /usr/share/lib/tmac/an default macro package ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWdoc | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ SEE ALSO
apropos(1), man(1), nroff(1), rdist(1), rm(1), troff(1), whatis(1), attributes(5), man(5), sgml(5) DIAGNOSTICS
man?/xxx.? (.so'ed from man?/yyy.?): No such file or directory The file outside the parentheses is missing, and is referred to by the file inside them. target of .so in man?/xxx.? must be relative to /usr/man catman only allows references to filenames that are relative to the directory /usr/man. opendir:man?: No such file or directory A harmless warning message indicating that one of the directories catman normally looks for is missing. *.*: No such file or directory A harmless warning message indicating catman came across an empty directory. WARNINGS
If a user, who has previously run catman to install the cat* directories, upgrades the operating system, the entire cat* directory struc- ture should be removed prior to running catman. See rm(1). Do not re-run catman to re-build the whatis database unless the complete set of man* directories is present. catman builds this windex file based on the man* directories. NOTES
To generate a valid windex index file, catman has certain requirements. Within the individual man page file, catman requires two macro lines to have a specific format. These are the .TH page heading line and the .SH NAME line. The .TH macro requires at least the first three arguments, that is, the filename, section number, and the date. The .TH line starts off with the .TH macro, followed by a space, the man page filename, a single space, the section number, another single space, and the date. The date should appear in double quotes and is specified as "day month year," with the month always abbreviated to the first three letters (Jan, Feb, Mar, and so forth). The .SH NAME macro, also known as the NAME line, must immediately follow the .TH line, with nothing in between those lines. No font changes are permitted in the NAME line. The NAME line is immediately followed by a line containing the man page filename; then shadow page names, if applicable, separated by commas; a dash; and a brief summary statement. These elements should all be on one line; no carriage returns are permitted. An example of proper coding of these lines is: .TH nismatch 1M "10 Apr 1998" .SH NAME nismatch, nisgrep - utilities for searching NIS+ tables SunOS 5.10 27 Feb 1998 catman(1M)
All times are GMT -4. The time now is 09:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy