Sponsored Content
Full Discussion: how to read man pages
Top Forums UNIX for Dummies Questions & Answers how to read man pages Post 302079176 by RTM on Friday 7th of July 2006 09:04:04 AM
Old 07-07-2006
Quote:
what does [[-aAdejflm]] mean?
Those are options which are explained in the man page
EXAMPLE:
Code:
The following options can be used with ps:

  -a  Prints information to standard output about all processes, except the
      session leaders and processes not associated with a terminal.

  -A  Writes information for all processes.

  -d  Prints information to standard output about all processes, except the
      session leaders.

Quote:
what does specifier mean?
Specifiers are explained in the ps man page
EXAMPLE:
Code:
Format Specifiers


  The following list contains all format specifiers that can be used with ps:

  ________________________________________________________________
  Specifier   Header	Meaning
  ________________________________________________________________
  acflag      ACFLG

			[Tru64 UNIX]  Process accounting flag
  args	      COMMAND	Command arguments
  c	      C		CPU utilization factor for scheduling


what does [=header mean] ?
RTM - it should be apparent by now....

Quote:
what does [-g glist] mean?
what does [-u ulist] mean?
From the ps man page:

Prints only information about processes that are in the process groups
listed in glist. The glist is a list of process-group identifiers
enclosed in " " (double quotes) and separated from one another by a
comma or one or more spaces (or tabs), or both.


The ulist argument is either a list of
user IDs or a list of user IDs enclosed in " " (double quotes) and
separated from one another by a comma or one or more spaces, or both.

You should really try reading the complete man page and then ask questions about it - all of the descriptions are in the man page (in this case).
 

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 creating

Hi, I wnat to create my own man pages, but I can't find a good description of the troff language. Knows somebaody a good docu including examples?? Thx Bensky (2 Replies)
Discussion started by: bensky
2 Replies

3. UNIX for Dummies Questions & Answers

man pages

Hi, I've written now a man pages, but I don't knwo how to get 'man' to view them. Where have I to put this files, which directories are allowed?? THX Bensky (3 Replies)
Discussion started by: bensky
3 Replies

4. 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

5. 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

6. Solaris

jumpstart and man pages

I've set up a jumpstart server on a Ultra 1 with 2 external 9GB hard drives. Below is the contents of the rules.ok file: Jserver# more rules.ok hostname jumpme - host_class - # version=2 checksum=2852 Below is the contents of the profile that I'm using for the test... (4 Replies)
Discussion started by: antalexi
4 Replies

7. Solaris

Solaris 10 man pages

Hi there, Ive just installed Solaris 10 from DVD and when trying to access the man pages, I get this # man ls No manual entry for ls. so I set MANPATH to /usr/share/man where all the man pages seem to be located, and i get the same result !!! Is there something else I have to do, ie... (5 Replies)
Discussion started by: hcclnoodles
5 Replies

8. 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

9. 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

10. Shell Programming and Scripting

Commands for man pages

what command should i use for displaying the manual pages for the socket, read and connect system calls? (1 Reply)
Discussion started by: Nabeel Nazir
1 Replies
PKILL(1)						    BSD General Commands Manual 						  PKILL(1)

NAME
pkill -- find or signal processes by name SYNOPSIS
pgrep [-filnvx] [-d delim] [-G gid] [-g pgrp] [-P ppid] [-s sid] [-t tty] [-U uid] [-u euid] pattern ... pkill [-signal] [-filnvx] [-G gid] [-g pgrp] [-P ppid] [-s sid] [-t tty] [-U uid] [-u euid] pattern ... prenice [-l] priority pattern ... DESCRIPTION
The pgrep command searches the process table on the running system and prints the process IDs of all processes that match the criteria given on the command line. The pkill command searches the process table on the running system and signals all processes that match the criteria given on the command line. The prenice command searches the process table on the running system and sets the priority of all processes that match the criteria given on the command line. The following options are available for pkill and pgrep: -d delim Specify a delimiter to be printed between each process ID. The default is a newline. This option can only be used with the pgrep command. -f Match against full argument lists. The default is to match against process names. -G gid Restrict matches to processes with a real group ID in the comma-separated list gid. -g pgrp Restrict matches to processes with a process group ID in the comma-separated list pgrp. The value zero is taken to mean the process group ID of the running pgrep or pkill command. -i Ignore case distinctions in both the process table and the supplied pattern. -l Long output. Print the process name in addition to the process ID for each matching process. If used in conjunction with -f, print the process ID and the full argument list for each matching process. -n Match only the most recently created process, if any. -P ppid Restrict matches to processes with a parent process ID in the comma-separated list ppid. -s sid Restrict matches to processes with a session ID in the comma-separated list sid. The value zero is taken to mean the session ID of the running pgrep or pkill command. -t tty Restrict matches to processes associated with a terminal in the comma-separated list tty. Terminal names may be specified as a fully qualified path, in the form 'ttyXX', or 'pts/N', (where XX is any pair of letters, and N is a number), or the shortened forms 'XX' or 'N'. A single dash ('-') matches processes not associated with a terminal. -U uid Restrict matches to processes with a real user ID in the comma-separated list uid. -u euid Restrict matches to processes with an effective user ID in the comma-separated list euid. -v Reverse the sense of the matching; display processes that do not match the given criteria. -x Require an exact match of the process name, or argument list if -f is given. The default is to match any substring. -signal A non-negative decimal number or symbolic signal name specifying the signal to be sent instead of the default TERM. This option is valid only when given as the first argument to pkill. The -l flag is also availale for prenice. Note that a running pgrep or pkill process will never consider itself or system processes (kernel threads) as a potential match. EXIT STATUS
pgrep, pkill, and prenice return one of the following values upon exit: 0 One or more processes were matched. 1 No processes were matched. 2 Invalid options were specified on the command line. 3 An internal error occurred. SEE ALSO
grep(1), kill(1), ps(1), kill(2), sigaction(2), re_format(7), signal(7), renice(8) HISTORY
pkill and pgrep first appeared in NetBSD 1.6. They are modelled after utilities of the same name that appeared in Sun Solaris 7. prenice was introduced in NetBSD 6.0. BSD
December 7, 2010 BSD
All times are GMT -4. The time now is 06:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy