Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Creating Custom man Page in Solaris Post 302292609 by candlejack on Saturday 28th of February 2009 10:27:41 PM
Old 02-28-2009
It was suggested here to try to put the man page in /usr/local/man and set your MANPATH env variable. Would this be possible?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how do you create a man page?

i've never done this before. i created a script that I placed in /usr/bin, but want to create a man page for it. i'm clueless thanks (3 Replies)
Discussion started by: theDirtiest
3 Replies

2. UNIX for Dummies Questions & Answers

adding a man page

I was wonderiong if ther is a way for a user to add a man page specific to thier account. similar to copying the .1 or .1.gz to /usr/share/man/man1 "cp *.1.gz /usr/share/man/man1". Except for using another folder as I don't have access to /usr/share/man/man1. I would think that this might involve... (1 Reply)
Discussion started by: jacob358
1 Replies

3. Red Hat

scp-1.2.27 man page

Hi Guys, I'm looking for the man page for scp version 1.2.27 I have an old redhat server that has a few large scripts that use this version and I want to know what the -A flag does and the man page is not on there. (4 Replies)
Discussion started by: Tornado
4 Replies

4. UNIX for Advanced & Expert Users

man page issue

Man page is not working my system. It is giving the following the following error > man ls gdbm fatal: read error with debug option > man -d ls ... .... ... ... using less as pager checking for locale en_US add_nls_manpath(): processing /usr/local/man:/usr/share/man:/usr/X11R6/man... (4 Replies)
Discussion started by: praveenkumar_l
4 Replies

5. Solaris

Unable to get help from man page

Help, it seem that i am unable to get man help form solaris 10. I am running SunOS unknown 5.10 Generic_120012-14 i86pc i386 i86pc when ever i try to man a command what i get is "No manual entry" like the one below. # man grep No manual entry for grep. # man ls No manual entry for ls.... (8 Replies)
Discussion started by: ezsurf
8 Replies

6. Solaris

Creating a Man page for a command

Hi, I would like to develop a man page as the one we usually get when we execute man <command name>. This man page will be for a samll utility that i have written. If this is not possible then what are the available possibilites for creating such help. thanks in advance. (2 Replies)
Discussion started by: raghu.amilineni
2 Replies

7. Solaris

man page question

What does the last change means in man page .. does that this man page has not been updated since 2003 or something else ? newfs-options The options are documented in the newfs man page. SunOS 5.10 Last change: 9 Dec 2003 1 System... (2 Replies)
Discussion started by: fugitive
2 Replies

8. Solaris

How to scroll through the man page in Solaris

Hey All, I generally login to the Solaris box using Putty. But when I read a man page, I am not being able to scroll line by line using traditional 'j' or 'k' keys. Any idea about how can we scroll through line by line while reading a manage page over Putty (2 Replies)
Discussion started by: paragkalra
2 Replies

9. UNIX for Dummies Questions & Answers

Changing Man page output

I've been asked to come up with a command to display a man page that will continuously scrol (i.e. not hitting space/enter)l. Is there a way do this? I'm stumped. Thank you for your help. (8 Replies)
Discussion started by: Opy99
8 Replies
MANPATH(5)							/etc/manpath.config							MANPATH(5)

NAME
manpath - format of the /etc/manpath.config file DESCRIPTION
The manpath configuration file is used by the manual page utilities to assess users' manpaths at run time, to indicate which manual page hierarchies (manpaths) are to be treated as system hierarchies and to assign them directories to be used for storing cat files. If the environment variable $MANPATH is already set, the information contained within /etc/manpath.config will not override it. FORMAT
The following field types are currently recognised: # comment Blank lines or those beginning with a # will be treated as comments and ignored. MANDATORY_MANPATH manpath_element Lines of this form indicate manpaths that every automatically generated $MANPATH should contain. This will typically include /usr/man. MANPATH_MAP path_element manpath_element Lines of this form set up $PATH to $MANPATH mappings. For each path_element found in the user's $PATH, manpath_element will be added to the $MANPATH. MANDB_MAP manpath_element [ catpath_element ] Lines of this form indicate which manpaths are to be treated as system manpaths, and optionally where their cat files should be stored. This field type is particularly important if man is a setuid program, as (when in the system configuration file /etc/man- path.config rather than the per-user configuration file .manpath) it indicates which manual page hierarchies to access as the setuid user and which as the invoking user. The system manual page hierarchies are usually those stored under /usr such as /usr/man, /usr/local/man and /usr/X11R6/man. If cat pages from a particular manpath_element are not to be stored or are to be stored in the traditional location, catpath_element may be omitted. Traditional cat placement would be impossible for read only mounted manual page hierarchies and because of this it is possible to specify any valid directory hierarchy for their storage. To observe the Linux FSSTND the keyword `FSSTND can be used in place of an actual directory. Unfortunately, it is necessary to specify all system man tree paths, including alternate operating system paths such as /usr/man/sun and any NLS locale paths such as /usr/man/de_DE.88591. As the information is parsed line by line in the order written, it is necessary for any manpath that is a sub-hierarchy of another hierarchy to be listed first, otherwise an incorrect match will be made. An example is that /usr/man/de_DE.88591 must come before /usr/man. DEFINE key value Lines of this form define miscellaneous configuration variables; see the default configuration file for those variables used by the manual pager utilities. They include default paths to various programs (such as grep and tbl), and default sets of arguments to those programs. SECTION section ... Lines of this form define the order in which manual sections should be searched. If there are no SECTION directives in the configu- ration file, the default is: SECTION 1 n l 8 3 0 2 5 4 9 6 7 If multiple SECTION directives are given, their section lists will be concatenated. If a particular extension is not in this list (say, 1mh) it will be displayed with the rest of the section it belongs to. The effect of this is that you only need to explicitly list extensions if you want to force a particular order. Sections with exten- sions should usually be adjacent to their main section (e.g. "1 1mh 8 ..."). SECTIONS is accepted as an alternative name for this directive. MINCATWIDTH width If the terminal width is less than width, cat pages will not be created (if missing) or displayed. The default is 80. MAXCATWIDTH width If the terminal width is greater than width, cat pages will not be created (if missing) or displayed. The default is 80. CATWIDTH width If width is non-zero, cat pages will always be formatted for a terminal of the given width, regardless of the width of the terminal actually being used. This should generally be within the range set by MINCATWIDTH and MAXCATWIDTH. NOCACHE This flag prevents man(1) from creating cat pages automatically. BUGS
Unless the rules above are followed and observed precisely, the manual pager utilities will not function as desired. The rules are overly complicated. 2.6.0.2 2011-04-13 MANPATH(5)
All times are GMT -4. The time now is 05:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy