Print this page 
7928 Add support for SMF_EXIT_TEMP_TRANSIENT
Split Close
Expand all
Collapse all
          --- old/usr/src/man/man5/smf_method.5
          +++ new/usr/src/man/man5/smf_method.5
   1    1  '\" te
   2    2  .\" Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved.
        3 +.\" Copyright 2015 RackTop Systems.
   3    4  .\" 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. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
   4    5  .\"  See the License for the specific language governing permissions and limitations under the License. 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
   5    6  .\" the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
   6      -.TH SMF_METHOD 5 "June 6, 2016"
        7 +.TH SMF_METHOD 5 "March 2, 2017"
   7    8  .SH NAME
   8    9  smf_method \- service management framework conventions for methods
   9   10  .SH DESCRIPTION
  10   11  .LP
  11   12  The class of services managed by \fBsvc.startd\fR(1M) in the service management
  12   13  framework, \fBsmf\fR(5), consists of applications that fit a simple
  13   14  \fBfork\fR(2)-\fBexec\fR(2) model. The \fBsvc.startd\fR(1M) master daemon and
  14   15  other restarters support the \fBfork\fR(2)-\fBexec\fR(2) model, potentially
  15   16  with additional capabilities. The \fBsvc.startd\fR(1M) daemon and other
  16   17  restarters require that the methods which activate, manipulate, or examine a
↓ open down ↓ 257 lines elided ↑ open up ↑ 
 274  275  T}
 275  276  \fBSMF_EXIT_ERR_CONFIG\fR       \fB96\fR        T{
 276  277  Unrecoverable configuration error. A common condition that returns this exit status is the absence of required configuration files for an enabled service instance.
 277  278  T}
 278  279  \fBSMF_EXIT_ERR_NOSMF\fR        \fB99\fR        T{
 279  280  Method has been mistakenly invoked outside the \fBsmf\fR(5) facility. Services that depend on \fBsmf\fR(5) capabilities should exit with this status value.
 280  281  T}
 281  282  \fBSMF_EXIT_ERR_PERM\fR \fB100\fR       T{
 282  283  Method requires a form of permission such as file access, privilege, authorization, or other credential that is not available when invoked.
 283  284  T}
      285 +\fBSMF_EXIT_TEMP_TRANSIENT\fR   \fB101\fR       T{
      286 +Method that is normally non-transient is temporarily transient.  This is not an error condition and a service returning this value will not be restarted.
      287 +T}
 284  288  \fBSMF_EXIT_ERR_OTHER\fR        \fBnon-zero\fR  T{
 285  289  Any non-zero exit status from a method is treated as an unknown error. A series of unknown errors can be diagnosed as a fault by the restarter or on behalf of the restarter.
 286  290  T}
 287  291  .TE
 288  292  
 289  293  .sp
 290  294  .LP
 291  295  Use of a precise exit code allows the responsible restarter to categorize an
 292  296  error response as likely to be intermittent and worth pursuing restart or
 293  297  permanent and request administrative intervention.
↓ open down ↓ 291 lines elided ↑ open up ↑ 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX