Print this page 
9696 add /etc/system.d support
Portions contributed by: Andy Fiddaman <andy@omniosce.org>
Reviewed by: Hans Rosenfeld <hans.rosenfeld@joyent.com>
Reviewed by: Peter Tribble <peter.tribble@gmail.com>
Reviewed by: C Fraire <cfraire@me.com>
Reviewed by: Toomas Soome <tsoome@me.com>
Split Close
Expand all
Collapse all
          --- old/usr/src/man/man4/system.4
          +++ new/usr/src/man/man4/system.4
   1    1  '\" te
   2    2  .\" Copyright (c) 2003 Sun Microsystems, Inc.  All Rights Reserved.
   3    3  .\" Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org>
        4 +.\" Copyright 2019 OmniOS Community Edition (OmniOSce) Association.
   4    5  .\" Copyright 1989 AT&T
   5    6  .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   6    7  .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   7    8  .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   8      -.TH SYSTEM 4 "Jan 25, 2016"
        9 +.TH SYSTEM 4 "Jan 29, 2019"
   9   10  .SH NAME
  10   11  system \- system configuration information file
  11   12  .SH DESCRIPTION
  12   13  .LP
  13   14  The \fBsystem\fR file is used for customizing the operation of the operating
  14   15  system kernel. The recommended procedure is to preserve the original
  15   16  \fBsystem\fR file before modifying it.
  16   17  .sp
  17   18  .LP
       19 +It is not recommended to edit the \fB/etc/system\fR file directly but rather
       20 +to deliver configuration fragments into files under \fB/etc/system.d\fR;
       21 +files in this directory are combined in alphabetical order and read by the
       22 +kernel before \fB/etc/system\fR is processed. Directives in \fB/etc/system\fR
       23 +therefore take precedence over any settings delivered in fragment files.
       24 +.sp
       25 +.LP
       26 +The recommended naming schema for the fragment files is to use the name of
       27 +the package which is delivering the file with '\fB/\fR' characters replaced
       28 +by '\fB:\fR'; file names that start with a dot (\fB.\fR) will be ignored.
       29 +.sp
       30 +.LP
       31 +If \fB/etc/system.d/\fR exists and contains any fragment files,
       32 +then the directory must also be writable or it will not be possible to
       33 +create or update the system boot archive.
       34 +.sp
       35 +.LP
  18   36  The \fBsystem\fR file contains commands which are read by the kernel during
  19   37  initialization and used to customize the operation of your system. These
  20   38  commands are useful for modifying the system's treatment of its loadable kernel
  21   39  modules.
  22   40  .sp
  23   41  .LP
  24   42  The syntax of the \fBsystem\fR file consists of a list of keyword/value pairs
  25   43  which are recognized by the system as valid commands. Comment lines must begin
  26   44  with an asterisk (\fB*\fR) or a hash mark (\fB#\fR) and end with a newline
  27   45  character. All commands are case-insensitive except where noted.
↓ open down ↓ 251 lines elided ↑ open up ↑ 
 279  297  .sp
 280  298  The only operation supported for modifying character pointers is simple
 281  299  assignment. Static string data such as character arrays cannot be modified
 282  300  using the \fBset\fR command. Use care and ensure that the variable you are
 283  301  modifying is in fact a character pointer. The \fBset\fR command is very
 284  302  powerful, and will likely cause problems if used carelessly. The following
 285  303  escape sequences are supported within the quoted string:
 286  304  .sp
 287  305  .in +2
 288  306  .nf
 289      -\en     (newline)
 290      -\et     (tab)
 291      -\eb     (backspace)
      307 +\en     (newline)
      308 +\et     (tab)
      309 +\eb     (backspace)
 292  310  .fi
 293  311  .in -2
 294  312  .sp
 295  313  
 296  314  .RE
 297  315  
 298  316  .SH EXAMPLES
 299  317  .LP
 300  318  \fBExample 1 \fRA sample \fBsystem\fR file.
 301  319  .sp
↓ open down ↓ 51 lines elided ↑ open up ↑ 
 353  371  .LP
 354  372  Use care when modifying the \fBsystem\fR file; it modifies the operation of the
 355  373  kernel. If you preserved the original \fBsystem\fR file, you can boot using
 356  374  \fBboot -a\fR, which will ask you to specify the path to the saved file. This
 357  375  should allow the system to boot correctly. If you cannot locate a \fBsystem\fR
 358  376  file that will work, you may specify \fB/dev/null\fR. This acts as an empty
 359  377  \fBsystem\fR file, and the system will attempt to boot using its default
 360  378  settings.
 361  379  .SH NOTES
 362  380  .LP
 363      -The \fB/etc/system\fR file is read only once, at boot time.
      381 +The \fBsystem\fR files are read only once, at boot time.
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX