Name Date Size #Lines LOC

..10-Dec-2021-

MakefileH A D14-Feb-20213.3 KiB165105

READMEH A D14-Feb-20211.4 KiB3732

README.shareH A D14-Feb-20215.9 KiB148111

boot-archiveH A D10-Dec-20211.5 KiB5313

boot-archive.xmlH A D14-Feb-20212.5 KiB9648

console-loginH A D14-Feb-20212.3 KiB8533

devices-audioH A D14-Feb-20211.3 KiB404

devices-audio.xmlH A D14-Feb-20212.3 KiB9245

devices-localH A D14-Feb-20212 KiB7626

devices-local.xmlH A D14-Feb-20213.1 KiB13376

early-manifest-import.xmlH A D14-Feb-20212.7 KiB10455

fs-localH A D14-Feb-20213.3 KiB11655

fs-minimalH A D14-Feb-20212.4 KiB8643

fs-rootH A D14-Feb-20214.7 KiB16469

fs-usrH A D14-Feb-20215.3 KiB190102

global.xmlH A D14-Feb-202128.2 KiB945885

identity-domainH A D14-Feb-20211.4 KiB4513

identity-nodeH A D14-Feb-20213 KiB9734

identity.xmlH A D14-Feb-20213 KiB12777

local-fs.xmlH A D14-Feb-20212.1 KiB8339

make-console-login-xmlH A D14-Feb-20219.1 KiB338272

manifest-importH A D14-Feb-202113.7 KiB506304

manifest-import.xmlH A D14-Feb-20212.3 KiB9143

minimal-fs.xmlH A D14-Feb-20212.3 KiB9446

multi-user-server.xmlH A D14-Feb-20213 KiB11349

multi-user.xmlH A D14-Feb-20213.7 KiB14577

name-services.xmlH A D14-Feb-20212.3 KiB9654

net-initH A D10-Dec-20213.1 KiB8719

net-installH A D14-Feb-202112.5 KiB486351

net-ipqosH A D14-Feb-20211.5 KiB495

net-iptunH A D14-Feb-20214.7 KiB16175

net-locH A D14-Feb-202118.2 KiB733427

net-loopbackH A D14-Feb-20212.2 KiB7428

net-netmaskH A D14-Feb-20212.3 KiB7714

net-nwamH A D14-Feb-202118.7 KiB647414

net-physicalH A D10-Dec-202115.8 KiB562306

net-routing-setupH A D10-Dec-20217.7 KiB22882

net-svcH A D14-Feb-20216.7 KiB271138

network-initial.xmlH A D14-Feb-20212.4 KiB9555

network-install.xmlH A D14-Feb-20218.9 KiB247200

network-ipqos.xmlH A D14-Feb-20212.5 KiB9955

network-iptun.xmlH A D14-Feb-20212.4 KiB9555

network-location.xmlH A D14-Feb-20216.5 KiB247142

network-loopback.xmlH A D14-Feb-20212 KiB7836

network-netcfg.xmlH A D14-Feb-20212.5 KiB10458

network-netmask.xmlH A D14-Feb-20212.9 KiB11770

network-physical.xmlH A D14-Feb-20214.7 KiB176117

network-routing-setup.xmlH A D14-Feb-20214.2 KiB14985

network-service.xmlH A D14-Feb-20213.3 KiB13071

network.xmlH A D14-Feb-20212.2 KiB9354

process-security.xmlH A D14-Feb-20212.8 KiB8746

restarter.xmlH A D14-Feb-202138.6 KiB1,3261,214

rmtmpfilesH A D14-Feb-20213.1 KiB8821

rmtmpfiles.xmlH A D14-Feb-20213.4 KiB13081

root-fs.xmlH A D14-Feb-20211.9 KiB7432

single-user.xmlH A D14-Feb-20213.5 KiB13879

sysconfig.xmlH A D14-Feb-20212.2 KiB8339

usr-fs.xmlH A D14-Feb-20212.3 KiB9245

vtdaemonH A D14-Feb-20211.3 KiB4613

vtdaemon.xmlH A D14-Feb-20213.3 KiB11167

README

1#
2# CDDL HEADER START
3#
4# The contents of this file are subject to the terms of the
5# Common Development and Distribution License, Version 1.0 only
6# (the "License").  You may not use this file except in compliance
7# with the License.
8#
9# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
10# or http://www.opensolaris.org/os/licensing.
11# See the License for the specific language governing permissions
12# and limitations under the License.
13#
14# When distributing Covered Code, include this CDDL HEADER in each
15# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
16# If applicable, add the following below this CDDL HEADER, with the
17# fields enclosed by brackets "[]" replaced with your own identifying
18# information: Portions Copyright [yyyy] [name of copyright owner]
19#
20# CDDL HEADER END
21#
22
23 Copyright 2004 Sun Microsystems, Inc.  All rights reserved.
24 Use is subject to license terms.
25Use is subject to license terms.
26
27ident	"%Z%%M%	%I%	%E% SMI"
28
29usr/src/cmd/svc/milestone/README
30
31This source directory contains service descriptions, in the form of XML
32manifests, for milestones and services that are required for the seed
33repository construction.  This includes most services required for
34satisfying the single-user milestone.  (In general, services associated
35with a specific command should locate their description in the directory
36that contains the source for that command.)
37

README.share

1#
2# CDDL HEADER START
3#
4# The contents of this file are subject to the terms of the
5# Common Development and Distribution License (the "License").
6# You may not use this file except in compliance with the License.
7#
8# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9# or http://www.opensolaris.org/os/licensing.
10# See the License for the specific language governing permissions
11# and limitations under the License.
12#
13# When distributing Covered Code, include this CDDL HEADER in each
14# file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15# If applicable, add the following below this CDDL HEADER, with the
16# fields enclosed by brackets "[]" replaced with your own identifying
17# information: Portions Copyright [yyyy] [name of copyright owner]
18#
19# CDDL HEADER END
20#
21
22Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
23Use is subject to license terms.
24
25/lib/svc/share/README
26
27smf(5):  Notes on maintenance mode and recovery
28
29Failures that bring the system to maintenance mode may include hardware
30or critical software failures.  The procedures below are given so that
31some software repairs can be made; the recommended exit approach once a
32repair has been made is to reboot the system.  The system can be brought
33to maintenance mode deliberately via the '-s' option to boot(1M), or via
34the 's' option to init(1M).
35
36In failure scenarios, smf(5) may or may not be running, depending on
37which component has failed.  If smf(5) is running, and the /usr
38filesystem is reachable, then the usual svcadm(1M) invocations to clear
39maintenance state and restart services instances can be used.
40Otherwise, the following instructions describe the direct execution of
41service methods, so that capabilities that svc.startd(1M) would normally
42start automatically can be started manually.  In the case that the
43document recommends an invocation like
44
45# /lib/svc/method/example-method start
46
47you may also consider running these scripts with the shell displaying
48the commands from the service method as they are executed.  For sh(1)
49based scripts, this would mean running the method as
50
51# /sbin/sh -x /lib/svc/method/example-method start
52
53Some methods may be written to instead use ksh(1), with invocation
54
55# /usr/bin/ksh -x /lib/svc/method/example-method start
56
57The first line of the service method script will generally specify its
58required interpreter using the standard #! notation.  Method scripts may
59potentially require interpreters other than sh(1) or ksh(1).
60
611.  Boot archive failure
62
63The boot archive may become out of sync with the root filesystem in a
64reboot following an abnormal system shutdown. The recommended action is
65to reboot immediately to rebuild the archive and correct the inconsistency.
66To accomplish this, on a GRUB-based platform, choose "Solaris failsafe"
67when the boot menu is displayed.  Type 'i' to get an interactive recovery
68shell and follow instructions to update the boot archive.  On an OBP-
69based platform, type 'boot -F failsafe' and follow the instructions.
70
71If the list of stale files are not yet loaded by the kernel
72or are compatible, you may continue booting by clearing the
73boot-archive service state
74
75# svcadm clear system/boot-archive
76
772.  Failure to mount filesystems.
78
79In cases where the system was unable to bring a combination of the
80system/filesystem/{root,usr,minimal} services online, it may be possible
81to directly execute the corresponding service methods
82
83# /lib/svc/method/fs-root
84# /lib/svc/method/fs-usr
85# /lib/svc/method/fs-minimal
86
87to mount the various filesystems.  In the case that these methods fail,
88a direct invocation of mount(1M), and potentially fsck(1M), should be
89attempted for file systems required for recovery purposes.
90
91/lib/svc/method/fs-usr attempts to remount the root file system
92read-write, such that persistent changes can be made to the system's
93configuration.  If this method is failing, one can directly remount
94using the mount(1M) command via
95
96# /sbin/mount -o rw,remount /
97
98/etc/svc/volatile is a temporary filesystem generally reserved for Sun
99private use.  It may prove a useful location to create mount points if
100the root file system cannot be remounted read-write.
101
1023.  Failure to run svc.configd(1M).
103
104svc.configd(1M) will give detailed instructions for recovery if the
105corruption is detected in the repository.  If svc.configd(1M) cannot be
106run because of missing or corrupt library components, then the affected
107components will need to be replaced.  Components could be copied from a
108CD-ROM or DVD-ROM, or from another system.
109
1104.  Failure to run svc.startd(1M).
111
112If the inittab(4) line to invoke svc.startd(1M) is missing or incorrect,
113it will need to be restored.  A valid entry is
114
115smf::sysinit:/lib/svc/bin/svc.startd    >/dev/msglog 2<>/dev/msglog </dev/console
116
117If svc.startd(1M) cannot be run because of missing or corrupt library
118components, then the affected components will need to be replaced, as
119for svc.configd(1M) above.
120
1215.  Activating basic networking configuration.
122
123If svc.startd(1M) did not execute successfully, it may also be necessary
124to activate network interfaces manually, such that other hosts can be
125contacted.  The service methods can be invoked directly as
126
127# /lib/svc/method/net-loopback
128# /lib/svc/method/net-physical
129
130If these methods fail, a direct invocation of ifconfig(1M) can be
131attempted.
132
133In some scenarios, one may be able to use routeadm(1M) to activate more
134dynamic route management functionality; restoring the default dynamic
135routing behaviour can be done using the '-u' option.  (Invoking routeadm
136with no arguments will display which commands must be accessible for the
137current routing configuration to be invoked.)  Otherwise, once
138interfaces are up, a default route can be manually added using the
139route(1M) command.  On typical IPv4 networks, this invocation would be
140
141# /sbin/route add net default _gateway_IP_
142
143--
144
145(An extended version of this document is available at
146http://illumos.org/msg/SMF-8000-QD.  That version includes additional
147document references.)
148