Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ././../../../../../../lib/svc/share/README
Real path: /lib/svc/share/README
Zurück

# # Copyright (c) 2004, 2016, Oracle and/or its affiliates. All rights reserved. # /lib/svc/share/README smf(7): Notes on maintenance mode and recovery Failures that bring the system to maintenance mode may include hardware or critical software failures. The procedures below are given so that some software repairs can be made; the recommended exit approach once a repair has been made is to reboot the system. The system can be brought to maintenance mode deliberately via the '-s' option to boot(8), or via the 's' option to init(8). In failure scenarios, smf(7) may or may not be running, depending on which component has failed. If smf(7) is running, then the usual svcadm(8) invocations to clear maintenance state and restart services instances can be used. Otherwise, the following instructions describe the direct execution of service methods, so that capabilities that svc.startd(8) would normally start automatically can be started manually. In the case that the document recommends an invocation like # /lib/svc/method/example-method start you may also consider running these scripts with the shell displaying the commands from the service method as they are executed. For sh(1) based scripts, this would mean running the method as # /sbin/sh -x /lib/svc/method/example-method start The first line of the service method script will generally specify its required interpreter using the standard #! notation. Method scripts may potentially require interpreters other than sh(1). 1. Boot archive failure The boot archive may become out of sync with the root filesystem in a reboot following an abnormal system shutdown. The recommended action is to reboot immediately to rebuild the archive and correct the inconsistency. If the list of stale files are not yet loaded by the kernel or are compatible, you may continue booting by clearing the boot-archive service state # svcadm clear system/boot-archive 2. Failure to mount filesystems. In cases where the system was unable to bring a combination of the system/filesystem/{root,usr,minimal} services online, it may be possible to directly execute the corresponding service methods # /lib/svc/method/fs-root # /lib/svc/method/fs-usr # /lib/svc/method/fs-minimal to mount the various filesystems. In the case that these methods fail, a direct invocation of mount(8), and potentially fsck(8), should be attempted for file systems required for recovery purposes. /lib/svc/method/fs-usr attempts to remount the root file system read-write, such that persistent changes can be made to the system's configuration. If this method is failing, one can directly remount using the mount(8) command via # /usr/sbin/mount -o rw,remount / /system/volatile is a temporary filesystem generally reserved for Oracle private use. It may prove a useful location to create mount points if the root file system cannot be remounted read-write. 3. Failure to run svc.configd(8). svc.configd(8) will give detailed instructions for recovery if the corruption is detected in the repository. If svc.configd(8) cannot be run because of missing or corrupt library components, then the affected components will need to be replaced via: # /usr/bin/pkg fix 4. Failure to run svc.startd(8). If the inittab(5) line to invoke svc.startd(8) is missing or incorrect, it will need to be restored. A valid entry is smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/console If svc.startd(8) cannot be run because of missing or corrupt library components, then the affected components will need to be replaced, as for svc.configd(8) above. 5. Activating basic networking configuration. If svc.startd(8) did not execute successfully, it may also be necessary to activate network interfaces manually, such that other hosts can be contacted. The service methods can be invoked directly as # /lib/svc/method/net-loopback # /lib/svc/method/net-physical If these methods fail, a direct invocation of ipadm(7) or dladm(7) can be attempted. In some scenarios, one may be able to use routeadm(8) to activate more dynamic route management functionality; restoring the default dynamic routing behaviour can be done using the '-u' option. (Invoking routeadm with no arguments will display which commands must be accessible for the current routing configuration to be invoked.) Otherwise, once interfaces are up, a default route can be manually added using the route(8) command. On typical IPv4 networks, this invocation would be # /usr/sbin/route add net default _gateway_IP_