4. ORACLE - SUN - SOLARIS - MAN PAGE (s) USER COMMANDS

|A| |B| |C| |D| |E| |F| |G| |H| |I| |J| |K| |L| |M| |N| |O| |P| |Q| |R| |S| |T| |U| |V| |W| |X| |Y| |Z|

choose a letter

D

• date(1)– write the date and time
• dc(1)– desk calculator
• deallocate(1)– device deallocation
• decrypt(1)– encrypt or decrypt files
• delta(1)– make a delta to an SCCS file
• deroff(1)– remove nroff/troff, tbl, and eqn constructs
• df(1B)– display status of disk space on file systems
• dhcpinfo(1)– display values of parameters received through DHCP
• diff(1)– compare two files
• diff3(1)– 3-way differential file comparison
• diffmk(1)– mark differences between versions of a troff input file
• digest(1)– calculate a message digest
• digestp(1)– frontends to the mp Text to PDL (Printer Description Language) pretty print filter
• dircmp(1)– directory comparison
• dirname(1)– deliver portions of path names
• dirs(1)– change working directory
• dis(1)– object code disassembler
• disable(1)– enable/disable LP printers
• dispgid(1)– displays a list of all valid group names
• dispuid(1)– displays a list of all valid user names
• dos2unix(1)– convert text file from DOS format to ISO format
• download(1)– host resident PostScript font downloader
• dpost(1)– troff postprocessor for PostScript printers
• dtappsession(1)– start a new Application Manager session
• du(1)– summarize disk usage
• du(1B)– display the number of disk blocks used per directory or file
• dumbplot(1B)– graphics filters for various plotters
• dump(1)– dump selected parts of an object file
• dumpcs(1)– show codeset table for the current locale
• dumpkeys(1)– load and dump keyboard translation tables

ORACLE SUN SOLARIS PAGES

Read More

3. ORACLE - SUN - SOLARIS - MAN PAGE (s) USER COMMANDS

|A| |B| |C| |D| |E| |F| |G| |H| |I| |J| |K| |L| |M| |N| |O| |P| |Q| |R| |S| |T| |U| |V| |W| |X| |Y| |Z|

choose a letter

C

• cal(1)– display a calendar
• calendar(1)– reminder service
• cancel(1)– cancel print request
• case(1)– shell command interpreter built-in commands
• cat(1)– concatenate and display files
• cc(1B)– C compiler
• cd(1)– change working directory
• cdc(1)– change the delta commentary of an SCCS delta
• cdrw(1)– CD read and write
• chdir(1)– change working directory
• checkeq(1)– typeset mathematics test
• checknr(1)– check nroff and troff input files; report possible errors
• chgrp(1)– change file group ownership
• chkey(1)– change user's secure RPC key pair
• chmod(1)– change the permissions mode of a file
• chown(1)– change file ownership
• chown(1B)– change owner
• ckdate(1)– prompts for and validates a date
• ckgid(1)– prompts for and validates a group id
• ckint(1)– display a prompt; verify and return an integer value
• ckitem(1)– build a menu; prompt for and return a menu item
• ckkeywd(1)– prompts for and validates a keyword
• ckpath(1)– display a prompt; verify and return a pathname
• ckrange(1)– prompts for and validates an integer
• ckstr(1)– display a prompt; verify and return a string answer
• cksum(1)– write file checksums and sizes
• cktime(1)– display a prompt; verify and return a time of day
• ckuid(1)– prompts for and validates a user ID
• ckyorn(1)– prompts for and validates yes/no
• clear(1)– clear the terminal screen
• cmp(1)– compare two files
• cocheck(1F)– communicate with a process
• cocreate(1F)– communicate with a process
• codestroy(1F)– communicate with a process
• col(1)– reverse line-feeds filter
• comb(1)– combine SCCS deltas
• comm(1)– select or reject lines common to two files
• command(1)– execute a simple command
• compress(1)– compress, uncompress files or display expanded files
• continue(1)– shell built-in functions to escape from or advance within a controlling while, for, foreach, or until loop
• coproc(1F)– communicate with a process
• coreceive(1F)– communicate with a process
• cosend(1F)– communicate with a process
• cp(1)– copy files
• cpio(1)– copy file archives in and out
• cpp(1)– the C language preprocessor
• cputrack(1)– monitor process and LWP behavior using CPU performance counters
• crle(1)– configure runtime linking environment
• crontab(1)– user crontab file
• crtplot(1B)– graphics filters for various plotters
• crypt(1)– encode or decode a file
• csh(1)– shell command interpreter with a C-like syntax
• csplit(1)– split files based on context
• ct(1C)– spawn login to a remote terminal
• ctags(1)– create a tags file for use with ex and vi
• ctrun(1)– execute command in a process contract
• ctstat(1)– display active system contracts
• ctwatch(1)– watch events in a contract or group of contracts
• cu(1C)– call another UNIX system
• cut(1)– cut out selected fields of each line of a file

ORACLE SUN SOLARIS MAN PAGES

Read More

2. ORACLE - SUN - SOLARIS - MAN PAGE (s) USER COMMANDS

|A| |B| |C| |D| |E| |F| |G| |H| |I| |J| |K| |L| |M| |N| |O| |P| |Q| |R| |S| |T| |U| |V| |W| |X| |Y| |Z|

choose a letter

B

• banner(1)– make posters
• basename(1)– deliver portions of path names
• basename(1B)– display portions of pathnames
• batch(1)– execute commands at a later time
• bc(1)– arbitrary precision arithmetic language
• bdiff(1)– big diff
• bfs(1)– big file scanner
• bg(1)– control process execution
• bgplot(1B)– graphics filters for various plotters
• biff(1B)– give notice of incoming mail messages
• break(1)– shell built-in functions to escape from or advance within a controlling while, for, foreach, or until loop

ORACLE SUN SOLARIS MAN PAGES

Read More

1. ORACLE - SUN - SOLARIS - MAN PAGE (s) USER COMMANDS

• PREFACE AND OVERVIEW =>
• INTRODUCTION =>
• LIVE MAN PAGE FOR USER COMMANDS =>

|A| |B| |C| |D| |E| |F| |G| |H| |I| |J| |K| |L| |M| |N| |O| |P| |Q| |R| |S| |T| |U| |V| |W| |X| |Y| |Z|

choose a letter
 

A

• acctcom(1)– search and print process accounting files
• adb(1)– general-purpose debugger
• addbib(1)– create or extend a bibliographic database
• admin(1)– create and administer SCCS history files
• aedplot(1B)– graphics filters for various plotters
• alias(1)– create or remove a pseudonym or shorthand for a command or series of commands
• allocate(1)– device allocation
• amt(1)– run abstract machine test
• answerbook2(1)– online documentation system
• appcert(1)– examine application-level products for unstable use of Solaris interfaces
• apptrace(1)– trace application function calls to Solaris shared libraries
• apropos(1)– locate commands by keyword lookup
• ar(1)– maintain portable archive or library
• arch(1)– display the architecture of the current host
• as(1)– assembler
• asa(1)– convert FORTRAN carriage-control output to printable form
• at(1)– execute commands at a later time
• atoplot(1B)– graphics filters for various plotters
• atq(1)– display the jobs queued to run at specified times
• atrm(1)– remove jobs spooled by at or batch
• audioconvert(1)– convert audio file formats
• audioplay(1)– play audio files
• audiorecord(1)– record an audio file
• auths(1)– print authorizations granted to a user
• auto_ef(1)– auto encoding finder
• awk(1)– pattern scanning and processing language

ORACLE SUN SOLARIS MAN PAGES

Read More

INTRODUCTION OF MAN PAGE IN SOLARIS OPERATING SYSTEM

• PREFACE AND OVERVIEW =>
• INTRODUCTION =>
• LIVE MAN PAGE FOR USER COMMANDS =>

 SOURCE

Name

Intro– introduction to commands and application programs

Description

This section describes, in alphabetical order, commands available with this operating system. Pages of special interest are categorized as follows:

1B

Commands found only in the SunOS/BSD Compatibility Package.

1C

Commands for communicating with other systems.

1F

Commands associated with Form and Menu Language Interpreter (FMLI).

1S

Commands specific to SunOS.

OTHER SECTIONS

See the following sections of the SunOS Reference Manual for more information.
• Section 1M for system maintenance commands.
  
• Section 4 for information on file formats.
  
• Section 5 for descriptions of publicly available files and miscellaneous information pages.
  
For tutorial information about these commands and procedures, see Solaris Advanced User’s Guide.

Manual Page Command Syntax

Unless otherwise noted, commands described in the SYNOPSIS section of a manual page accept options and other arguments according to the following syntax and should be interpreted as explained below. name [-option...] [cmdarg...] where:

[ ]

Surround an option or cmdarg that is not required.

...

Indicates multiple occurrences of the option or cmdarg.

name

The name of an executable file.

{ }

The options and/or arguments enclosed within braces are interdependent, such that everything enclosed must be treated as a unit.

option

(Always preceded by a “-”.) noargletter... or, argletter optarg[,...]

noargletter

A single letter representing an option without an option-argument. Notice that more than one noargletter option can be grouped after one “-” (Guideline 5, below).

argletter

A single letter representing an option requiring an option-argument.

optarg

An option-argument (character string) satisfying a preceding argletter. Notice that groups of optargs following an argletter must be separated by commas, or separated by a tab or space character and quoted (Guideline 8, below).

cmdarg

Path name (or other command argument) not beginning with “-”, or “-” by itself indicating the standard input.

Unless otherwise specified, whenever an operand or option-argument is, or contains, a numeric value:

• The number is interpreted as a decimal integer.
  
• Numerals in the range 0 to 2147483647 are syntactically recognized as numeric values.
  
• When the utility description states that it accepts negative numbers as operands or option-arguments, numerals in the range -2147483647 to 2147483647 are syntactically recognized as numeric values.
  
• Ranges greater than those listed here are allowed.
  

Command Syntax Standard: Guidelines

These command syntax guidelines are not followed by all current commands, but new commands are likely to obey them. getopts(1) should be used by all shell procedures to parse positional parameters and to check for legal options. It supports Guidelines 3-10 below. The enforcement of the other guidelines must be done by the command itself.
1. Command names (name above) should be between two and nine characters long.
   
2. Command names should include only lower-case letters and digits.
   
3. Option names (option above) must be one character long.
   
4. All options must be preceded by “-”.
   
5. Options with no arguments can be grouped after a single “-”.
   
6. The first option-argument (optarg above) following an option must be preceded by a tab or space character.
   
7. Option-arguments cannot be optional.
   
8. Groups of option-arguments following an option must either be separated by commas or separated by tab or space character and quoted (-o xxx,z,yy or -o“xxx z yy”).
   
9. All options must precede operands (cmdarg above) on the command line.
   
10. “- -” can be used to indicate the end of the options.
    
11. The order of the options relative to one another should not matter.
    
12. The relative order of the operands (cmdarg above) can affect their significance in ways determined by the command with which they appear.
    
13. “-” preceded and followed by a white space character should only be used to mean standard input.
    
An expanded set of guidelines referred to as CLIP for Command Line Interface Paradigm has been developed for Solaris and other Sun products. Its intent is to provide a command line syntax more closely aligned with the GNU command line syntax popular on Linux systems.There is no intent to retrofit existing utilities or even to apply this to all new utilities. It is only intended to be applied to sets of utilities being developed when appropriate. CLIP is a full superset of the guidelines discussed above which are closely aligned with IEEE Std. 1003.1-2001 (SUSv3). It does not include all the GNU syntax. The GNU syntax allows constructs that either conflict with the IEEE rules or are ambiguous. These constructs are not allowed. The expanded CLIP command line syntax is:

utility_name -a --longopt1 -c option_argument \ -f option_argument --longopt2=option_argument \ --longopt3 option_argument operand

The utility in the example is named utility_name. It is followed by options, option-arguments, and operands, collectively referred to as arguments. The arguments that consist of a hyphen followed a single letter or digit, such as -a, are known as short-options . The arguments that consist of two hyphens followed by a series of letters, digits and hyphens, such as --longopt1, are known as long-options . Collectively, short-options and long-options are referred to as options (or historically, flags ). Certain options are followed by an option-argument, as shown with -c option_argument . The arguments following the last options and option-arguments are named operands. Once the first operand is encountered, all subsequent arguments are interpreted to be operands. Option-arguments are sometimes shown separated from their short-options by BLANKSs, sometimes directly adjacent. This reflects the situation that in some cases an option-argument is included within the same argument string as the option; in most cases it is the next argument. This specification requires that the option be a separate argument from its option-argument, but there are some exceptions to ensure continued operation of historical applications:
• If the SYNOPSIS of a utility shows a SPACE between a short-option and option-argument (as with -c option_argument in the example), the application uses separate arguments for that option and its option-argument.
  
• If a SPACE is not shown (as with -f option_argument in the example), the application expects an option and its option-argument directly adjacent in the same argument string, without intervening BLANKs.
  
• Notwithstanding the preceding requirements, an application should accept short-options and option-arguments as a single argument or as separate arguments whether or not a SPACE is shown on the synopsis line.
  
• Long-options with option-arguments are always documented as using an equals sign as the separator between the option name and the option-argument. If the OPTIONS section of a utility shows an equals sign (=) between a long-option and its option-argument (as with --longopt2= option_argument in the example), a application shall also permit the use of separate arguments for that option and its option-argument (as with --longopt1 option_argument in the example).
  
CLIP expands the guidelines discussed with the following additional guidelines:

14.

The form command subcommand [options] [operands] is appropriate for grouping similar operations. Subcommand names should follow the same conventions as command names as specified in guidelines 1 and 2.

15.

Long-options should be preceded by -- and should include only alphanumeric characters and hyphens from the portable character set. Option names are typically one to three words long, with hyphens to separate words.

16.

--name=argument should be used to specify an option-argument for a long-option. The form --name argument is also accepted.

17.

All utilities should support two standard long-options: --version (with the short-option synonym -V ) and --help (with the short-option synonym -? ). The short option synonyms for --version can vary if the preferred synonym is already in use (but a synonym shall be provided). Both of these options stop further argument processing when encountered and after displaying the appropriate output, the utility successfully exits.

18.

Every short-option should have exactly one corresponding long-option and every long-option should have exactly one corresponding short-option. Synonymous options can be allowed in the interest of compatibility with historical practice or community versions of equivalent utilities.

19.

The short-option name should get its name from the long-option name according to these rules:

1. Use the first letter of the long-option name for the short-option name.
   
2. If the first letter conflicts with other short-option names, choose a prominent consonant.
   
3. If the first letter and the prominent consonant conflict with other shortoption names, choose a prominent vowel.
   
4. If none of the letters of the long-option name are usable, select an arbitrary character.
   

20.

If a long-option name consists of a single character, it must use the same character as the short-option name. Single character long-options should be avoided. They are only allowed for the exceptionally rare case that a single character is the most descriptive name.

21.

The subcommand in the form described in guideline 1 of the additional CLIP guidelines is generally required. In the case where it is omitted, the command shall take no operands and only options which are defined to stop further argument processing when encountered are allowed. Invoking a command of this form without a subcommand and no arguments is an error. This guideline is provided to allow the common forms command --help, command -?, command --version, and command -V to be accepted in the command-subcommand construct.

Several of these guidelines are only of interest to the authors of utilities. They are provided here for the use of anyone wanting to author utilities following this syntax.

Attributes

See attributes(5) for a discussion of the attributes listed in this section.

See Also

getopts(1), wait(1), exit(2), getopt(3C), wait(3UCB), attributes(5)

Diagnostics

Upon termination, each command returns two bytes of status, one supplied by the system and giving the cause for termination, and (in the case of “normal” termination) one supplied by the program [see wait(3UCB) and exit(2)]. The former byte is 0 for normal termination. The latter byte is customarily 0 for successful execution and non-zero to indicate troubles such as erroneous parameters, or bad or inaccessible data. It is called variously “exit code”, “exit status”, or “return code”, and is described only where special conventions are involved.

Warnings

Some commands produce unexpected results when processing files containing null characters. These commands often treat text input lines as strings and therefore become confused upon encountering a null character (the string terminator) within a line. SOURCE

Read More

PREFACE AND OVERVIEW OF SOLARIS USER COMMANDS MAN PAGES

• PREFACE AND OVERVIEW =>
• INTRODUCTION =>
• MAN PAGE FOR USER COMMANDS =>

  SOURCE
  

  Preface

  Both novice users and those familar with the SunOS operating system can use online man pages to obtain information about the system and its features. A man page is intended to answer concisely the question “What does it do?” The man pages in general comprise a reference manual. They are not intended to be a tutorial.
  

  Overview

  The following contains a brief description of each man page section and the information it references:
  
• Section 1 describes, in alphabetical order, commands available with the operating system.
  
• Section 1M describes, in alphabetical order, commands that are used chiefly for system maintenance and administration purposes.
  
• Section 2 describes all of the system calls. Most of these calls have one or more error returns. An error condition is indicated by an otherwise impossible returned value.
  
• Section 3 describes functions found in various libraries, other than those functions that directly invoke UNIX system primitives, which are described in Section 2.
  
• Section 4 outlines the formats of various files. The C structure declarations for the file formats are given where applicable.
  
• Section 5 contains miscellaneous documentation such as character-set tables.
  
• Section 6 contains available games and demos.
  
• Section 7 describes various special files that refer to specific hardware peripherals and device drivers. STREAMS software drivers, modules and the STREAMS-generic set of system calls are also described.
  
• Section 9 provides reference information needed to write device drivers in the kernel environment. It describes two device driver interface specifications: the Device Driver Interface (DDI) and the Driver/Kernel Interface (DKI).
  
• Section 9E describes the DDI/DKI, DDI-only, and DKI-only entry-point routines a developer can include in a device driver.
  
• Section 9F describes the kernel functions available for use by device drivers.
  
• Section 9S describes the data structures used by drivers to share information between the driver and the kernel.
  

Below is a generic format for man pages. The man pages of each manual section generally follow this order, but include only needed headings. For example, if there are no bugs to report, there is no BUGS section. See the intro pages for more information and detail about each section, and man(1) for more information about man pages in general.

NAME

This section gives the names of the commands or functions documented, followed by a brief description of what they do.

SYNOPSIS

This section shows the syntax of commands or functions. When a command or file does not exist in the standard path, its full path name is shown. Options and arguments are alphabetized, with single letter arguments first, and options with arguments next, unless a different argument order is required. The following special characters are used in this section:

[ ]

Brackets. The option or argument enclosed in these brackets is optional. If the brackets are omitted, the argument must be specified.

. . .

Ellipses. Several values can be provided for the previous argument, or the previous argument can be specified multiple times, for example, "filename . . ." .

|

Separator. Only one of the arguments separated by this character can be specified at a time.

{ }

Braces. The options and/or arguments enclosed within braces are interdependent, such that everything enclosed must be treated as a unit.

PROTOCOL

This section occurs only in subsection 3R to indicate the protocol description file.

DESCRIPTION

This section defines the functionality and behavior of the service. Thus it describes concisely what the command does. It does not discuss OPTIONS or cite EXAMPLES. Interactive commands, subcommands, requests, macros, and functions are described under USAGE.

IOCTL

This section appears on pages in Section 7 only. Only the device class that supplies appropriate parameters to the ioctl(2) system call is called ioctl and generates its own heading. ioctl calls for a specific device are listed alphabetically (on the man page for that specific device). ioctl calls are used for a particular class of devices all of which have an io ending, such as mtio(7I).

OPTIONS

This secton lists the command options with a concise summary of what each option does. The options are listed literally and in the order they appear in the SYNOPSIS section. Possible arguments to options are discussed under the option, and where appropriate, default values are supplied.

OPERANDS

This section lists the command operands and describes how they affect the actions of the command.

OUTPUT

This section describes the output – standard output, standard error, or output files – generated by the command.

RETURN VALUES

If the man page documents functions that return values, this section lists these values and describes the conditions under which they are returned. If a function can return only constant values, such as 0 or –1, these values are listed in tagged paragraphs. Otherwise, a single paragraph describes the return values of each function. Functions declared void do not return values, so they are not discussed in RETURN VALUES.

ERRORS

On failure, most functions place an error code in the global variable errno indicating why they failed. This section lists alphabetically all error codes a function can generate and describes the conditions that cause each error. When more than one condition can cause the same error, each condition is described in a separate paragraph under the error code.

USAGE

This section lists special rules, features, and commands that require in-depth explanations. The subsections listed here are used to explain built-in functionality:

Commands

Modifiers

Variables

Expressions

Input Grammar

EXAMPLES

This section provides examples of usage or of how to use a command or function. Wherever possible a complete example including command-line entry and machine response is shown. Whenever an example is given, the prompt is shown as example%, or if the user must be superuser, example#. Examples are followed by explanations, variable substitution rules, or returned values. Most examples illustrate concepts from the SYNOPSIS, DESCRIPTION, OPTIONS, and USAGE sections.

ENVIRONMENT VARIABLES

This section lists any environment variables that the command or function affects, followed by a brief description of the effect.

EXIT STATUS

This section lists the values the command returns to the calling program or shell and the conditions that cause these values to be returned. Usually, zero is returned for successful completion, and values other than zero for various error conditions.

FILES

This section lists all file names referred to by the man page, files of interest, and files created or required by commands. Each is followed by a descriptive summary or explanation.

ATTRIBUTES

This section lists characteristics of commands, utilities, and device drivers by defining the attribute type and its corresponding value. See attributes(5) for more information.

SEE ALSO

This section lists references to other man pages, in-house documentation, and outside publications.

DIAGNOSTICS

This section lists diagnostic messages with a brief explanation of the condition causing the error.

WARNINGS

This section lists warnings about special conditions which could seriously affect your working conditions. This is not a list of diagnostics.

NOTES

This section lists additional information that does not belong anywhere else on the page. It takes the form of an aside to the user, covering points of special interest. Critical information is never covered here.

BUGS

This section describes known bugs and, wherever possible, suggests workarounds.

SOURCE

Read More

ORACLE - SUN - SOLARIS - MAN PAGE (s)

 This is help you to get the online MAN Pages of every user commands in ORACLE SUN SOLARIS Operating System (SPARC / X86).

• PREFACE AND OVERVIEW =>
• INTRODUCTION =>
• MAN PAGE OF USER COMMANDS =>

Read More

testing

click

man pages section 1: User Commands

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

• A
  • acctcom(1)– search and print process accounting files
  • adb(1)– general-purpose debugger
  • addbib(1)– create or extend a bibliographic database
  • admin(1)– create and administer SCCS history files
  • aedplot(1B)– graphics filters for various plotters
  • alias(1)– create or remove a pseudonym or shorthand for a command or series of commands
  • allocate(1)– device allocation
  • amt(1)– run abstract machine test
  • answerbook2(1)– online documentation system
  • appcert(1)– examine application-level products for unstable use of Solaris interfaces
  • apptrace(1)– trace application function calls to Solaris shared libraries
  • apropos(1)– locate commands by keyword lookup
  • ar(1)– maintain portable archive or library
  • arch(1)– display the architecture of the current host
  • as(1)– assembler
  • asa(1)– convert FORTRAN carriage-control output to printable form
  • at(1)– execute commands at a later time
  • atoplot(1B)– graphics filters for various plotters
  • atq(1)– display the jobs queued to run at specified times
  • atrm(1)– remove jobs spooled by at or batch
  • audioconvert(1)– convert audio file formats
  • audioplay(1)– play audio files
  • audiorecord(1)– record an audio file
  • auths(1)– print authorizations granted to a user
  • auto_ef(1)– auto encoding finder
  • awk(1)– pattern scanning and processing language

Read More