1Intro(1M) System Administration Commands Intro(1M)
2
6 Intro, intro - introduction to maintenance commands and application
7 programs
8
10 This section describes, in alphabetical order, commands that are used
11 chiefly for system maintenance and administration purposes.
12 Because of command restructuring for the Virtual File System architec‐
15 ture, there are several instances of multiple manual pages that begin
16 with the same name. For example, the mount, pages − mount(1M),
17 mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), and
18 mount_ufs(1M). In each such case the first of the multiple pages
19 describes the syntax and options of the generic command, that is, those
20 options applicable to all FSTypes (file system types). The succeeding
21 pages describe the functionality of the FSType-specific modules of the
22 command. These pages list the command followed by an underscore ( _ )
23 and the FSType to which they pertain. Note that the administrator
24 should not attempt to call these modules directly. The generic command
25 provides a common interface to all of them. Thus the FSType-specific
26 manual pages should not be viewed as describing distinct commands, but
27 rather as detailing those aspects of a command that are specific to a
28 particular FSType.
29
31 Unless otherwise noted, commands described in this section accept
32 options and other arguments according to the following syntax:
33 name [option(s)] [cmdarg(s)]
35 where:
39 name The name of an executable file.
41 option − noargletter(s) or,
44 − argletter<>optarg
46 where <> is optional white space.
48 noargletter A single letter representing an option without an argu‐
51 ment.
52 argletter A single letter representing an option requiring an
55 argument.
56 optarg Argument (character string) satisfying preceding arglet‐
59 ter.
60 cmdarg Pathname (or other command argument) not beginning with
63 − or, − by itself indicating the standard input.
64
67 See attributes(5) for a discussion of the attributes listed in this
68 section.
69
71 Sun Microsystems, Inc. gratefully acknowledges The Open Group for per‐
72 mission to reproduce portions of its copyrighted documentation. Origi‐
73 nal documentation from The Open Group can be obtained online at
74 http://www.opengroup.org/bookstore/.
75 The Institute of Electrical and Electronics Engineers and The Open
78 Group, have given us permission to reprint portions of their documenta‐
79 tion.
80 In the following statement, the phrase ``this text'' refers to portions
83 of the system documentation.
84 Portions of this text are reprinted and reproduced in electronic form
87 in the SunOS Reference Manual, from IEEE Std 1003.1, 2004 Edition,
88 Standard for Information Technology -- Portable Operating System Inter‐
89 face (POSIX), The Open Group Base Specifications Issue 6, Copyright (C)
90 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc
91 and The Open Group. In the event of any discrepancy between these ver‐
92 sions and the original IEEE and The Open Group Standard, the original
93 IEEE and The Open Group Standard is the referee document. The original
94 Standard can be obtained online at http://www.open‐
95 group.org/unix/online.html.
96 This notice shall appear on any product containing this material.
99
101 getopt(1), getopt(3C), attributes(5)
102
104 Upon termination, each command returns 0 for normal termination and
105 non-zero to indicate troubles such as erroneous parameters, bad or
106 inaccessible data, or other inability to cope with the task at hand. It
107 is called variously ``exit code,'' ``exit status,'' or ``return code,''
108 and is described only where special conventions are involved.
109
111 Unfortunately, not all commands adhere to the standard syntax.
112SunOS 5.11 17 Nov 2008 Intro(1M)