Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Where do I find what commands I can use? Post 11831 by peter.herlihy on Wednesday 12th of December 2001 05:10:27 PM
Old 12-12-2001
A command I found useful when learning was:

man -k keyword

This command accesses man (the manual) using the -k option will search for entries that have your keyword in the description or command - and obviously keyword is where you put in the word.

For example - searching for commands that will let you copy a file....type

man -k copy

This will list heaps of commands and descriptions - then if you find a command in here that you want to use - or find more about type:

man command

Hope this helps.Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

find commands?

what comand do I use to find usefull comands, common comands? or, where on www? if noone knows, then what comand do I use to run a (bin)file? (3 Replies)
Discussion started by: hallrobe
3 Replies

2. UNIX for Dummies Questions & Answers

Unix Find commands

thank you for the help (1 Reply)
Discussion started by: scooter17
1 Replies

3. UNIX for Dummies Questions & Answers

find and grep commands

I'm having trouble with the following commands i. count the number of lines which end in a 4 letter word grep '{4\}$' bfile <<seems to print out everything abc abc abcd joe joe john bob bill gregory greg greg gregory the grep command prints out the lines with 4 letter words and the... (3 Replies)
Discussion started by: StrengthThaDon
3 Replies

4. Shell Programming and Scripting

find filenames like unix commands

Hi, I need to write a small script to search in some specific directories to check if any file is present with a unix command name... Means if the directory contains any files like cat, vi, grep, find etc i need to list those files into a file. Please help Thanks, D (6 Replies)
Discussion started by: deepakgang
6 Replies

5. Shell Programming and Scripting

Need help in find and cp commands

I m using the below command for finding a particular file using grep and then copy it. But the the below command esp the cp is not working find . -name "CurrentCollector*" -exec grep -l '300173680000D1A8' {} \; | xargs cp {} /ednpdtu7/u01/pipe/current_reprocess - It's giving the particular... (5 Replies)
Discussion started by: ali560045
5 Replies

6. Shell Programming and Scripting

Execute multiple commands in a find

I am checking that a file is older than a reference file that I build with a touch command before processing it. If it is not old enough, I want to sleep for an hour and check again. My problem is if it is old enough to process, I want to exit when I am done, but I cannot find a way to exit... (2 Replies)
Discussion started by: prismtx
2 Replies

7. UNIX for Dummies Questions & Answers

Find & If commands together

Hi to everybody!! I have a (simple) question but i am newbie with unix and so i need a little help...I am writing a bash script file and i want to put inside this: i have this command " find /usr/bin -name bzip2 -print " that i want to put it in a "if" statement and when it returns true the... (6 Replies)
Discussion started by: orestis7
6 Replies

8. UNIX for Advanced & Expert Users

I need help to find some unix commands

Hey everyone, I need some help for some unix commands. - List all processes in the file "ProcessUser.txt" sorted by the users and in the file "ProcessName.txt" sorted by the name of the process. - How much time does the command "ls -alR /" need and compared to that, how much time is... (2 Replies)
Discussion started by: ZOCKER3000
2 Replies

9. UNIX for Dummies Questions & Answers

Find process by name and insert commands

I am writing a tcsh script that will open an already-running processs on a system, and give it a command. I want to have something similar to this: http://www.cyberciti.biz/faq/kill-process-in-linux-or-terminate-a-process-in-unix-or-linux-systems/ But I need to be able to find the process and... (5 Replies)
Discussion started by: Adorai
5 Replies

10. Shell Programming and Scripting

Find commands help

hi gurus, I need a example. I am looking for a source code. where I got the keyword "altria_fetch" and also the keyword is present in the file ".pc" files. and it is present in the directory /fast folder. Inside fast there are lot of sub directories present on it. I am not sure how to reach... (8 Replies)
Discussion started by: ramkumar15
8 Replies
MAN.CONF(5)						      BSD File Formats Manual						       MAN.CONF(5)

NAME
man.conf -- configuration file for manual pages DESCRIPTION
The man.conf file contains the default configuration used by man(1), apropos(1), whatis(1), catman(8), and makewhatis(8) to find manual pages and information about manual pages (e.g. the whatis database). Manual pages are located by searching an ordered set of directories called the ``man path'' for a file that matches the name of the requested page. Each directory in the search path usually has a set of subdirectories in it (though this is not required). When subdirectories are used, there are normally two subdirectories for each section of the manual. One subdirectory contains formatted copies of that section's manual pages that can be directly displayed to a terminal, while the other section subdirectory contains unformatted copies of the pages (see nroff(1) and mdoc(7)). Formatted manual pages are normally named with a trailing ``.0'' suffix. The man.conf file contains comment and configuration lines. Comment lines start with the ``#'' character. Blank lines are also treated as comment lines. Configuration lines consist of a configuration keyword followed by a configuration string. There are two types of configura- tion keywords: control keywords and section keywords. Control keywords must start with the ``_'' character. The following control keywords are currently defined: _build identifies the set of suffixes used for manual pages that must be formatted for display and the command that should be used to for- mat them. Manual file names, regardless of their format, are expected to end in a ``.*'' pattern, i.e. a ``.'' followed by some suffix. The first field of a _build line contains a man page suffix specification. The suffix specification may contain the nor- mal shell globbing characters (NOT including curly braces (``{}'')). The rest of the _build line is a shell command line whose standard output is a formatted manual page that can be directly displayed to the user. There should be exactly one occurrence of the string ``%s'' in the shell command line, and it will be replaced by the name of the file which is being formatted. _crunch used by catman(8) to determine how to crunch formatted pages which originally were compressed man pages: The first field lists a suffix which indicates what kind of compression were used to compress the man page. The rest of the line must be a shell command line, used to compress the formatted pages. There should be exactly one occurrence of the string ``%s'' in the shell command line, and it will be replaced by the name of the output file. _default contains the system-wide default man path used to search for man pages. _subdir contains the list (in search order) of section subdirectories which will be searched in any man path directory named with a trail- ing slash (``/'') character. This list is also used, even if there is no trailing slash character, when a path is specified to the man(1) utility by the user, by the MANPATH environment variable, or by the -M and -m options. _suffix identifies the set of suffixes used for formatted man pages (the ``.0'' suffix is normally used here). Formatted man pages can be directly displayed to the user. Each suffix may contain the normal shell globbing characters (NOT including curly braces (``{}'')). _version contains the version of the configuration file. _whatdb defines the full pathname (not just a directory path) for a database to be used by the apropos(1) and whatis(1) commands. The pathname may contain the normal shell globbing characters, including curly braces (``{}''); to escape a shell globbing character, precede it with a backslash (``''). Section configuration lines in man.conf consist of a section keyword naming the section and a configuration string that defines the directory or subdirectory path that the section's manual pages are located in. The path may contain the normal shell globbing characters, including curly braces (``{}''); to escape a shell globbing character, precede it with a backslash (``''). Section keywords must not start with the ``_'' character. A section path may contain either a list of absolute directories or a list of or relative directories (but not both). Relative directory paths are treated as a list of subdirectories that are appended to the current man path directory being searched. Section configuration lines with absolute directory paths (starting with ``/'') completely replace the current man search path directory with their content. Section configuration lines with absolute directory paths ending with a trailing slash character are expected to contain subdirectories of manual pages, (see the keyword ``_subdir'' above). The ``_subdir'' subdirectory list is not applied to absolute section directories if there is no trailing slash. In addition to the above rules, the man(1) command also always checks in each directory that it searches for a subdirectory with the same name as the current machine type. If the machine-specific directory is found, it is also searched. This allows the manual to contain machine-specific man pages. Note that the machine subdirectory does not need to be specified in the man.conf file. Multiple specifications for all types of man.conf configuration lines are cumulative and the entries are used in the order listed in the file; multiple entries may be listed per line, as well. FILES
/etc/man.conf Standard manual configuration file. EXAMPLES
Given the following man.conf file: _version BSD.2 _subdir cat[123] _suffix .0 _build .[1-9] nroff -man %s _build .tbl tbl %s | nroff -man _default /usr/share/man/ sect3 /usr/share/man/{old/,}cat3 By default, the command ``man mktemp'' will search for ``mktemp.<any_digit>'' and ``mktemp.tbl'' in the directories ``/usr/share/man/cat1'', ``/usr/share/man/cat2'', and ``/usr/share/man/cat3''. If on a machine of type ``vax'', the subdirectory ``vax'' in each directory would be searched as well, before the directory was searched. If ``mktemp.tbl'' was found first, the command ``tbl <manual page> | nroff -man'' would be run to build a man page for display to the user. The command ``man sect3 mktemp'' would search the directories ``/usr/share/man/old/cat3'' and ``/usr/share/man/cat3'', in that order, for the mktemp manual page. If a subdirectory with the same name as the current machine type existed in any of them, it would be searched as well, before each of them were searched. SEE ALSO
apropos(1), machine(1), man(1), whatis(1), whereis(1), fnmatch(3), glob(3), catman(8), makewhatis(8) BSD
December 27, 2011 BSD
All times are GMT -4. The time now is 05:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy