Advertisement
Guest User

Untitled

a guest
Jan 2nd, 2016
79
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 33.67 KB | None | 0 0
  1. MAN(1) Manual pager utils MAN(1)
  2.  
  3. NAME
  4. man - an interface to the on-line reference manuals
  5.  
  6. SYNOPSIS
  7. man [-C file] [-d] [-D] [--warnings[=warnings]] [-R encoding] [-L locale] [-m system[,...]] [-M path] [-S list] [-e extension] [-i|-I] [--regex|--wild‐
  8. card] [--names-only] [-a] [-u] [--no-subpages] [-P pager] [-r prompt] [-7] [-E encoding] [--no-hyphenation] [--no-justification] [-p string] [-t]
  9. [-T[device]] [-H[browser]] [-X[dpi]] [-Z] [[section] page ...] ...
  10. man -k [apropos options] regexp ...
  11. man -K [-w|-W] [-S list] [-i|-I] [--regex] [section] term ...
  12. man -f [whatis options] page ...
  13. man -l [-C file] [-d] [-D] [--warnings[=warnings]] [-R encoding] [-L locale] [-P pager] [-r prompt] [-7] [-E encoding] [-p string] [-t] [-T[device]]
  14. [-H[browser]] [-X[dpi]] [-Z] file ...
  15. man -w|-W [-C file] [-d] [-D] page ...
  16. man -c [-C file] [-d] [-D] page ...
  17. man [-?V]
  18.  
  19. DESCRIPTION
  20. man is the system's manual pager. Each page argument given to man is normally the name of a program, utility or function. The manual page associated
  21. with each of these arguments is then found and displayed. A section, if provided, will direct man to look only in that section of the manual. The
  22. default action is to search in all of the available sections following a pre-defined order ("1 1p 8 2 3 3p 4 5 6 7 9 0p tcl n l p o 1x 2x 3x 4x 5x 6x 7x
  23. 8x" by default, unless overridden by the SECTION directive in /etc/man_db.conf), and to show only the first page found, even if page exists in several
  24. sections.
  25.  
  26. The table below shows the section numbers of the manual followed by the types of pages they contain.
  27.  
  28. 1 Executable programs or shell commands
  29. 2 System calls (functions provided by the kernel)
  30. 3 Library calls (functions within program libraries)
  31. 4 Special files (usually found in /dev)
  32. 5 File formats and conventions eg /etc/passwd
  33. 6 Games
  34. 7 Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7)
  35. 8 System administration commands (usually only for root)
  36. 9 Kernel routines [Non standard]
  37.  
  38. A manual page consists of several sections.
  39.  
  40. Conventional section names include NAME, SYNOPSIS, CONFIGURATION, DESCRIPTION, OPTIONS, EXIT STATUS, RETURN VALUE, ERRORS, ENVIRONMENT, FILES, VERSIONS,
  41. CONFORMING TO, NOTES, BUGS, EXAMPLE, AUTHORS, and SEE ALSO.
  42.  
  43. The following conventions apply to the SYNOPSIS section and can be used as a guide in other sections.
  44.  
  45. bold text type exactly as shown.
  46. italic text replace with appropriate argument.
  47. [-abc] any or all arguments within [ ] are optional.
  48. -a|-b options delimited by | cannot be used together.
  49. argument ... argument is repeatable.
  50. [expression] ... entire expression within [ ] is repeatable.
  51.  
  52. Exact rendering may vary depending on the output device. For instance, man will usually not be able to render italics when running in a terminal, and
  53. will typically use underlined or coloured text instead.
  54.  
  55. The command or function illustration is a pattern that should match all possible invocations. In some cases it is advisable to illustrate several exclu‐
  56. sive invocations as is shown in the SYNOPSIS section of this manual page.
  57.  
  58. EXAMPLES
  59. man ls
  60. Display the manual page for the item (program) ls.
  61.  
  62. man -a intro
  63. Display, in succession, all of the available intro manual pages contained within the manual. It is possible to quit between successive displays or
  64. skip any of them.
  65.  
  66. man -t alias | lpr -Pps
  67. Format the manual page referenced by `alias', usually a shell manual page, into the default troff or groff format and pipe it to the printer named ps.
  68. The default output for groff is usually PostScript. man --help should advise as to which processor is bound to the -t option.
  69.  
  70. man -l -Tdvi ./foo.1x.gz > ./foo.1x.dvi
  71. This command will decompress and format the nroff source manual page ./foo.1x.gz into a device independent (dvi) file. The redirection is necessary
  72. as the -T flag causes output to be directed to stdout with no pager. The output could be viewed with a program such as xdvi or further processed into
  73. PostScript using a program such as dvips.
  74.  
  75. man -k printf
  76. Search the short descriptions and manual page names for the keyword printf as regular expression. Print out any matches. Equivalent to apro‐
  77. pos printf.
  78.  
  79. man -f smail
  80. Lookup the manual pages referenced by smail and print out the short descriptions of any found. Equivalent to whatis smail.
  81.  
  82. OVERVIEW
  83. Many options are available to man in order to give as much flexibility as possible to the user. Changes can be made to the search path, section order,
  84. output processor, and other behaviours and operations detailed below.
  85.  
  86. If set, various environment variables are interrogated to determine the operation of man. It is possible to set the `catch all' variable $MANOPT to any
  87. string in command line format with the exception that any spaces used as part of an option's argument must be escaped (preceded by a backslash). man will
  88. parse $MANOPT prior to parsing its own command line. Those options requiring an argument will be overridden by the same options found on the command
  89. line. To reset all of the options set in $MANOPT, -D can be specified as the initial command line option. This will allow man to `forget' about the
  90. options specified in $MANOPT although they must still have been valid.
  91.  
  92. The manual pager utilities packaged as man-db make extensive use of index database caches. These caches contain information such as where each manual
  93. page can be found on the filesystem and what its whatis (short one line description of the man page) contains, and allow man to run faster than if it had
  94. to search the filesystem each time to find the appropriate manual page. If requested using the -u option, man will ensure that the caches remain consis‐
  95. tent, which can obviate the need to manually run software to update traditional whatis text databases.
  96.  
  97. If man cannot find a mandb initiated index database for a particular manual page hierarchy, it will still search for the requested manual pages, although
  98. file globbing will be necessary to search within that hierarchy. If whatis or apropos fails to find an index it will try to extract information from a
  99. traditional whatis database instead.
  100.  
  101. These utilities support compressed source nroff files having, by default, the extensions of .Z, .z and .gz. It is possible to deal with any compression
  102. extension, but this information must be known at compile time. Also, by default, any cat pages produced are compressed using gzip. Each `global' manual
  103. page hierarchy such as /usr/share/man or /usr/X11R6/man may have any directory as its cat page hierarchy. Traditionally the cat pages are stored under
  104. the same hierarchy as the man pages, but for reasons such as those specified in the File Hierarchy Standard (FHS), it may be better to store them else‐
  105. where. For details on how to do this, please read manpath(5). For details on why to do this, read the standard.
  106.  
  107. International support is available with this package. Native language manual pages are accessible (if available on your system) via use of locale func‐
  108. tions. To activate such support, it is necessary to set either $LC_MESSAGES, $LANG or another system dependent environment variable to your language
  109. locale, usually specified in the POSIX 1003.1 based format:
  110.  
  111. <language>[_<territory>[.<character-set>[,<version>]]]
  112.  
  113. If the desired page is available in your locale, it will be displayed in lieu of the standard (usually American English) page.
  114.  
  115. Support for international message catalogues is also featured in this package and can be activated in the same way, again if available. If you find that
  116. the manual pages and message catalogues supplied with this package are not available in your native language and you would like to supply them, please
  117. contact the maintainer who will be coordinating such activity.
  118.  
  119. For information regarding other features and extensions available with this manual pager, please read the documents supplied with the package.
  120.  
  121. DEFAULTS
  122. man will search for the desired manual pages within the index database caches. If the -u option is given, a cache consistency check is performed to ensure
  123. the databases accurately reflect the filesystem. If this option is always given, it is not generally necessary to run mandb after the caches are ini‐
  124. tially created, unless a cache becomes corrupt. However, the cache consistency check can be slow on systems with many manual pages installed, so it is
  125. not performed by default, and system administrators may wish to run mandb every week or so to keep the database caches fresh. To forestall problems
  126. caused by outdated caches, man will fall back to file globbing if a cache lookup fails, just as it would if no cache was present.
  127.  
  128. Once a manual page has been located, a check is performed to find out if a relative preformatted `cat' file already exists and is newer than the nroff
  129. file. If it does and is, this preformatted file is (usually) decompressed and then displayed, via use of a pager. The pager can be specified in a number
  130. of ways, or else will fall back to a default is used (see option -P for details). If no cat is found or is older than the nroff file, the nroff is fil‐
  131. tered through various programs and is shown immediately.
  132.  
  133. If a cat file can be produced (a relative cat directory exists and has appropriate permissions), man will compress and store the cat file in the back‐
  134. ground.
  135.  
  136. The filters are deciphered by a number of means. Firstly, the command line option -p or the environment variable $MANROFFSEQ is interrogated. If -p was
  137. not used and the environment variable was not set, the initial line of the nroff file is parsed for a preprocessor string. To contain a valid preproces‐
  138. sor string, the first line must resemble
  139.  
  140. '\" <string>
  141.  
  142. where string can be any combination of letters described by option -p below.
  143.  
  144. If none of the above methods provide any filter information, a default set is used.
  145.  
  146. A formatting pipeline is formed from the filters and the primary formatter (nroff or [tg]roff with -t) and executed. Alternatively, if an executable pro‐
  147. gram mandb_nfmt (or mandb_tfmt with -t) exists in the man tree root, it is executed instead. It gets passed the manual source file, the preprocessor
  148. string, and optionally the device specified with -T or -E as arguments.
  149.  
  150. OPTIONS
  151. Non argument options that are duplicated either on the command line, in $MANOPT, or both, are not harmful. For options that require an argument, each
  152. duplication will override the previous argument value.
  153.  
  154. General options
  155. -C file, --config-file=file
  156. Use this user configuration file rather than the default of ~/.manpath.
  157.  
  158. -d, --debug
  159. Print debugging information.
  160.  
  161. -D, --default
  162. This option is normally issued as the very first option and resets man's behaviour to its default. Its use is to reset those options that may have
  163. been set in $MANOPT. Any options that follow -D will have their usual effect.
  164.  
  165. --warnings[=warnings]
  166. Enable warnings from groff. This may be used to perform sanity checks on the source text of manual pages. warnings is a comma-separated list of
  167. warning names; if it is not supplied, the default is "mac". See the “Warnings” node in info groff for a list of available warning names.
  168.  
  169. Main modes of operation
  170. -f, --whatis
  171. Equivalent to whatis. Display a short description from the manual page, if available. See whatis(1) for details.
  172.  
  173. -k, --apropos
  174. Equivalent to apropos. Search the short manual page descriptions for keywords and display any matches. See apropos(1) for details.
  175.  
  176. -K, --global-apropos
  177. Search for text in all manual pages. This is a brute-force search, and is likely to take some time; if you can, you should specify a section to
  178. reduce the number of pages that need to be searched. Search terms may be simple strings (the default), or regular expressions if the --regex
  179. option is used.
  180.  
  181. -l, --local-file
  182. Activate `local' mode. Format and display local manual files instead of searching through the system's manual collection. Each manual page argu‐
  183. ment will be interpreted as an nroff source file in the correct format. No cat file is produced. If '-' is listed as one of the arguments, input
  184. will be taken from stdin. When this option is not used, and man fails to find the page required, before displaying the error message, it attempts
  185. to act as if this option was supplied, using the name as a filename and looking for an exact match.
  186.  
  187. -w, --where, --path, --location
  188. Don't actually display the manual pages, but do print the location(s) of the source nroff files that would be formatted.
  189.  
  190. -W, --where-cat, --location-cat
  191. Don't actually display the manual pages, but do print the location(s) of the cat files that would be displayed. If -w and -W are both specified,
  192. print both separated by a space.
  193.  
  194. -c, --catman
  195. This option is not for general use and should only be used by the catman program.
  196.  
  197. -R encoding, --recode=encoding
  198. Instead of formatting the manual page in the usual way, output its source converted to the specified encoding. If you already know the encoding of
  199. the source file, you can also use manconv(1) directly. However, this option allows you to convert several manual pages to a single encoding with‐
  200. out having to explicitly state the encoding of each, provided that they were already installed in a structure similar to a manual page hierarchy.
  201.  
  202. Finding manual pages
  203. -L locale, --locale=locale
  204. man will normally determine your current locale by a call to the C function setlocale(3) which interrogates various environment variables, possibly
  205. including $LC_MESSAGES and $LANG. To temporarily override the determined value, use this option to supply a locale string directly to man. Note
  206. that it will not take effect until the search for pages actually begins. Output such as the help message will always be displayed in the initially
  207. determined locale.
  208.  
  209. -m system[,...], --systems=system[,...]
  210. If this system has access to other operating system's manual pages, they can be accessed using this option. To search for a manual page from
  211. NewOS's manual page collection, use the option -m NewOS.
  212.  
  213. The system specified can be a combination of comma delimited operating system names. To include a search of the native operating system's manual
  214. pages, include the system name man in the argument string. This option will override the $SYSTEM environment variable.
  215.  
  216. -M path, --manpath=path
  217. Specify an alternate manpath to use. By default, man uses manpath derived code to determine the path to search. This option overrides the $MAN‐
  218. PATH environment variable and causes option -m to be ignored.
  219.  
  220. A path specified as a manpath must be the root of a manual page hierarchy structured into sections as described in the man-db manual (under "The
  221. manual page system"). To view manual pages outside such hierarchies, see the -l option.
  222.  
  223. -S list, -s list, --sections=list
  224. List is a colon- or comma-separated list of `order specific' manual sections to search. This option overrides the $MANSECT environment variable.
  225. (The -s spelling is for compatibility with System V.)
  226.  
  227. -e sub-extension, --extension=sub-extension
  228. Some systems incorporate large packages of manual pages, such as those that accompany the Tcl package, into the main manual page hierarchy. To get
  229. around the problem of having two manual pages with the same name such as exit(3), the Tcl pages were usually all assigned to section l. As this is
  230. unfortunate, it is now possible to put the pages in the correct section, and to assign a specific `extension' to them, in this case, exit(3tcl).
  231. Under normal operation, man will display exit(3) in preference to exit(3tcl). To negotiate this situation and to avoid having to know which sec‐
  232. tion the page you require resides in, it is now possible to give man a sub-extension string indicating which package the page must belong to.
  233. Using the above example, supplying the option -e tcl to man will restrict the search to pages having an extension of *tcl.
  234.  
  235. -i, --ignore-case
  236. Ignore case when searching for manual pages. This is the default.
  237.  
  238. -I, --match-case
  239. Search for manual pages case-sensitively.
  240.  
  241. --regex
  242. Show all pages with any part of either their names or their descriptions matching each page argument as a regular expression, as with apropos(1).
  243. Since there is usually no reasonable way to pick a "best" page when searching for a regular expression, this option implies -a.
  244.  
  245. --wildcard
  246. Show all pages with any part of either their names or their descriptions matching each page argument using shell-style wildcards, as with apro‐
  247. pos(1) --wildcard. The page argument must match the entire name or description, or match on word boundaries in the description. Since there is
  248. usually no reasonable way to pick a "best" page when searching for a wildcard, this option implies -a.
  249.  
  250. --names-only
  251. If the --regex or --wildcard option is used, match only page names, not page descriptions, as with whatis(1). Otherwise, no effect.
  252.  
  253. -a, --all
  254. By default, man will exit after displaying the most suitable manual page it finds. Using this option forces man to display all the manual pages
  255. with names that match the search criteria.
  256.  
  257. -u, --update
  258. This option causes man to perform an `inode level' consistency check on its database caches to ensure that they are an accurate representation of
  259. the filesystem. It will only have a useful effect if man is installed with the setuid bit set.
  260.  
  261. --no-subpages
  262. By default, man will try to interpret pairs of manual page names given on the command line as equivalent to a single manual page name containing a
  263. hyphen or an underscore. This supports the common pattern of programs that implement a number of subcommands, allowing them to provide manual
  264. pages for each that can be accessed using similar syntax as would be used to invoke the subcommands themselves. For example:
  265.  
  266. $ man -aw git diff
  267. /usr/share/man/man1/git-diff.1.gz
  268.  
  269. To disable this behaviour, use the --no-subpages option.
  270.  
  271. $ man -aw --no-subpages git diff
  272. /usr/share/man/man1/git.1.gz
  273. /usr/share/man/man3/Git.3pm.gz
  274. /usr/share/man/man1/diff.1.gz
  275.  
  276. Controlling formatted output
  277. -P pager, --pager=pager
  278. Specify which output pager to use. By default, man uses less. This option overrides the $MANPAGER environment variable, which in turn overrides
  279. the $PAGER environment variable. It is not used in conjunction with -f or -k.
  280.  
  281. The value may be a simple command name or a command with arguments, and may use shell quoting (backslashes, single quotes, or double quotes). It
  282. may not use pipes to connect multiple commands; if you need that, use a wrapper script, which may take the file to display either as an argument or
  283. on standard input.
  284.  
  285. -r prompt, --prompt=prompt
  286. If a recent version of less is used as the pager, man will attempt to set its prompt and some sensible options. The default prompt looks like
  287.  
  288. Manual page name(sec) line x
  289.  
  290. where name denotes the manual page name, sec denotes the section it was found under and x the current line number. This is achieved by using the
  291. $LESS environment variable.
  292.  
  293. Supplying -r with a string will override this default. The string may contain the text $MAN_PN which will be expanded to the name of the current
  294. manual page and its section name surrounded by `(' and `)'. The string used to produce the default could be expressed as
  295.  
  296. \ Manual\ page\ \$MAN_PN\ ?ltline\ %lt?L/%L.:
  297. byte\ %bB?s/%s..?\ (END):?pB\ %pB\\%..
  298. (press h for help or q to quit)
  299.  
  300. It is broken into three lines here for the sake of readability only. For its meaning see the less(1) manual page. The prompt string is first
  301. evaluated by the shell. All double quotes, back-quotes and backslashes in the prompt must be escaped by a preceding backslash. The prompt string
  302. may end in an escaped $ which may be followed by further options for less. By default man sets the -ix8 options.
  303.  
  304. The $MANLESS environment variable described below may be used to set a default prompt string if none is supplied on the command line.
  305.  
  306. -7, --ascii
  307. When viewing a pure ascii(7) manual page on a 7 bit terminal or terminal emulator, some characters may not display correctly when using the
  308. latin1(7) device description with GNU nroff. This option allows pure ascii manual pages to be displayed in ascii with the latin1 device. It will
  309. not translate any latin1 text. The following table shows the translations performed: some parts of it may only be displayed properly when using
  310. GNU nroff's latin1(7) device.
  311.  
  312. Description Octal latin1 ascii
  313. ─────────────────────────────────────────────
  314. continuation hyphen 255 ‐ -
  315. bullet (middle dot) 267 · o
  316. acute accent 264 ´ '
  317. multiplication sign 327 × x
  318.  
  319. If the latin1 column displays correctly, your terminal may be set up for latin1 characters and this option is not necessary. If the latin1 and
  320. ascii columns are identical, you are reading this page using this option or man did not format this page using the latin1 device description. If
  321. the latin1 column is missing or corrupt, you may need to view manual pages with this option.
  322.  
  323. This option is ignored when using options -t, -H, -T, or -Z and may be useless for nroff other than GNU's.
  324.  
  325. -E encoding, --encoding=encoding
  326. Generate output for a character encoding other than the default. For backward compatibility, encoding may be an nroff device such as ascii,
  327. latin1, or utf8 as well as a true character encoding such as UTF-8.
  328.  
  329. --no-hyphenation, --nh
  330. Normally, nroff will automatically hyphenate text at line breaks even in words that do not contain hyphens, if it is necessary to do so to lay out
  331. words on a line without excessive spacing. This option disables automatic hyphenation, so words will only be hyphenated if they already contain
  332. hyphens.
  333.  
  334. If you are writing a manual page and simply want to prevent nroff from hyphenating a word at an inappropriate point, do not use this option, but
  335. consult the nroff documentation instead; for instance, you can put "\%" inside a word to indicate that it may be hyphenated at that point, or put
  336. "\%" at the start of a word to prevent it from being hyphenated.
  337.  
  338. --no-justification, --nj
  339. Normally, nroff will automatically justify text to both margins. This option disables full justification, leaving justified only to the left mar‐
  340. gin, sometimes called "ragged-right" text.
  341.  
  342. If you are writing a manual page and simply want to prevent nroff from justifying certain paragraphs, do not use this option, but consult the nroff
  343. documentation instead; for instance, you can use the ".na", ".nf", ".fi", and ".ad" requests to temporarily disable adjusting and filling.
  344.  
  345. -p string, --preprocessor=string
  346. Specify the sequence of preprocessors to run before nroff or troff/groff. Not all installations will have a full set of preprocessors. Some of
  347. the preprocessors and the letters used to designate them are: eqn (e), grap (g), pic (p), tbl (t), vgrind (v), refer (r). This option overrides
  348. the $MANROFFSEQ environment variable. zsoelim is always run as the very first preprocessor.
  349.  
  350. -t, --troff
  351. Use groff -mandoc to format the manual page to stdout. This option is not required in conjunction with -H, -T, or -Z.
  352.  
  353. -T[device], --troff-device[=device]
  354. This option is used to change groff (or possibly troff's) output to be suitable for a device other than the default. It implies -t. Examples
  355. (provided with Groff-1.17) include dvi, latin1, ps, utf8, X75 and X100.
  356.  
  357. -H[browser], --html[=browser]
  358. This option will cause groff to produce HTML output, and will display that output in a web browser. The choice of browser is determined by the
  359. optional browser argument if one is provided, by the $BROWSER environment variable, or by a compile-time default if that is unset (usually lynx).
  360. This option implies -t, and will only work with GNU troff.
  361.  
  362. -X[dpi], --gxditview[=dpi]
  363. This option displays the output of groff in a graphical window using the gxditview program. The dpi (dots per inch) may be 75, 75-12, 100, or
  364. 100-12, defaulting to 75; the -12 variants use a 12-point base font. This option implies -T with the X75, X75-12, X100, or X100-12 device respec‐
  365. tively.
  366.  
  367. -Z, --ditroff
  368. groff will run troff and then use an appropriate post-processor to produce output suitable for the chosen device. If groff -mandoc is groff, this
  369. option is passed to groff and will suppress the use of a post-processor. It implies -t.
  370.  
  371. Getting help
  372. -?, --help
  373. Print a help message and exit.
  374.  
  375. --usage
  376. Print a short usage message and exit.
  377.  
  378. -V, --version
  379. Display version information.
  380.  
  381. EXIT STATUS
  382. 0 Successful program execution.
  383.  
  384. 1 Usage, syntax or configuration file error.
  385.  
  386. 2 Operational error.
  387.  
  388. 3 A child process returned a non-zero exit status.
  389.  
  390. 16 At least one of the pages/files/keywords didn't exist or wasn't matched.
  391.  
  392. ENVIRONMENT
  393. MANPATH
  394. If $MANPATH is set, its value is used as the path to search for manual pages.
  395.  
  396. MANROFFOPT
  397. The contents of $MANROFFOPT are added to the command line every time man invokes the formatter (nroff, troff, or groff).
  398.  
  399. MANROFFSEQ
  400. If $MANROFFSEQ is set, its value is used to determine the set of preprocessors to pass each manual page through. The default preprocessor list is
  401. system dependent.
  402.  
  403. MANSECT
  404. If $MANSECT is set, its value is a colon-delimited list of sections and it is used to determine which manual sections to search and in what order.
  405. The default is "1 1p 8 2 3 3p 4 5 6 7 9 0p tcl n l p o 1x 2x 3x 4x 5x 6x 7x 8x", unless overridden by the SECTION directive in /etc/man_db.conf.
  406.  
  407. MANPAGER, PAGER
  408. If $MANPAGER or $PAGER is set ($MANPAGER is used in preference), its value is used as the name of the program used to display the manual page. By
  409. default, less is used.
  410.  
  411. The value may be a simple command name or a command with arguments, and may use shell quoting (backslashes, single quotes, or double quotes). It
  412. may not use pipes to connect multiple commands; if you need that, use a wrapper script, which may take the file to display either as an argument or
  413. on standard input.
  414.  
  415. MANLESS
  416. If $MANLESS is set, its value will be used as the default prompt string for the less pager, as if it had been passed using the -r option (so any
  417. occurrences of the text $MAN_PN will be expanded in the same way). For example, if you want to set the prompt string unconditionally to “my prompt
  418. string”, set $MANLESS to ‘-Psmy prompt string’. Using the -r option overrides this environment variable.
  419.  
  420. BROWSER
  421. If $BROWSER is set, its value is a colon-delimited list of commands, each of which in turn is used to try to start a web browser for man --html.
  422. In each command, %s is replaced by a filename containing the HTML output from groff, %% is replaced by a single percent sign (%), and %c is
  423. replaced by a colon (:).
  424.  
  425. SYSTEM If $SYSTEM is set, it will have the same effect as if it had been specified as the argument to the -m option.
  426.  
  427. MANOPT If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format. As all of the other man specific envi‐
  428. ronment variables can be expressed as command line options, and are thus candidates for being included in $MANOPT it is expected that they will
  429. become obsolete. N.B. All spaces that should be interpreted as part of an option's argument must be escaped.
  430.  
  431. MANWIDTH
  432. If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be for‐
  433. matted with a line length appropriate to the current terminal (using the value of $COLUMNS, an ioctl(2) if available, or falling back to 80 charac‐
  434. ters if neither is available). Cat pages will only be saved when the default formatting can be used, that is when the terminal line length is
  435. between 66 and 80 characters.
  436.  
  437. MAN_KEEP_FORMATTING
  438. Normally, when output is not being directed to a terminal (such as to a file or a pipe), formatting characters are discarded to make it easier to
  439. read the result without special tools. However, if $MAN_KEEP_FORMATTING is set to any non-empty value, these formatting characters are retained.
  440. This may be useful for wrappers around man that can interpret formatting characters.
  441.  
  442. MAN_KEEP_STDERR
  443. Normally, when output is being directed to a terminal (usually to a pager), any error output from the command used to produce formatted versions of
  444. manual pages is discarded to avoid interfering with the pager's display. Programs such as groff often produce relatively minor error messages
  445. about typographical problems such as poor alignment, which are unsightly and generally confusing when displayed along with the manual page. How‐
  446. ever, some users want to see them anyway, so, if $MAN_KEEP_STDERR is set to any non-empty value, error output will be displayed as usual.
  447.  
  448. LANG, LC_MESSAGES
  449. Depending on system and implementation, either or both of $LANG and $LC_MESSAGES will be interrogated for the current message locale. man will
  450. display its messages in that locale (if available). See setlocale(3) for precise details.
  451.  
  452. FILES
  453. /etc/man_db.conf
  454. man-db configuration file.
  455.  
  456. /usr/share/man
  457. A global manual page hierarchy.
  458.  
  459. /usr/share/man/index.(bt|db|dir|pag)
  460. A traditional global index database cache.
  461.  
  462. /var/cache/man/index.(bt|db|dir|pag)
  463. An FHS compliant global index database cache.
  464.  
  465. SEE ALSO
  466. apropos(1), groff(1), less(1), manpath(1), nroff(1), troff(1), whatis(1), zsoelim(1), setlocale(3), manpath(5), ascii(7), latin1(7), man(7), catman(8),
  467. mandb(8), the man-db package manual, FSSTND
  468.  
  469. HISTORY
  470. 1990, 1991 – Originally written by John W. Eaton (jwe@che.utexas.edu).
  471.  
  472. Dec 23 1992: Rik Faith (faith@cs.unc.edu) applied bug fixes supplied by Willem Kasdorp (wkasdo@nikhefk.nikef.nl).
  473.  
  474. 30th April 1994 – 23rd February 2000: Wilf. (G.Wilford@ee.surrey.ac.uk) has been developing and maintaining this package with the help of a few dedicated
  475. people.
  476.  
  477. 30th October 1996 – 30th March 2001: Fabrizio Polacco <fpolacco@debian.org> maintained and enhanced this package for the Debian project, with the help of
  478. all the community.
  479.  
  480. 31st March 2001 – present day: Colin Watson <cjwatson@debian.org> is now developing and maintaining man-db.
  481.  
  482. 2.7.5 2015-11-06 MAN(1)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement