Solaris OS single-user mode with critical file systems mounted and accessible.
1
The system is running in a single-user administrative state with access to all available file systems.
2
multi-user
The system is supporting multiuser operations. Multiple users can access the system. All system daemons are running except for the Network File System (NFS) server and some other network resource server related daemons.
3
multi-user-server
The system is supporting multiuser operations and has NFS resource sharing and other network resource servers available.
4
This level is currently not implemented.
5
A transitional run level in which the Solaris OS is shut down and the system is powered off.
6
A transitional run level in which the Solaris OS is shut down and the system reboots to the default run level.
To know which runlevel you're in, use this command:
Make a copy of the /etc/system file before saving changes. If the file is incorrect, you won't be able to boot. If you have a problem with the modified file, here's the solution to repair:
Executes the process before the init process tries to access the console (for example, the console login prompt). The init process waits for completion of the process before it continues to read the inittab file.
powerfail
Executes the process only if the init process receives a power fail signal.
The svc.startd daemon is the replacement for init. To view the current configuration:
#!/sbin/sh## Copyright 2004 Sun Microsystems, Inc. All rights reserved.# Use is subject to license terms.## ident "@(#)newservice 1.14 04/08/30 SMI"case"$1"in'start')/usr/bin/newservice&;;'stop')/usr/bin/pkill-x-u0newservice
;;*)echo"Usage: PAGECONTENT { start | stop }";;esacexit0
<?xml version="1.0"?><!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1"><!-- Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. ident "@(#)newservice.xml 1.2 04/09/13 SMI"--><service_bundletype='manifest'name='OPTnew:newservice'><servicename='site/newservice'type='service'version='1'><single_instance/><exec_methodtype='method'name='start'exec='/lib/svc/method/newservice start'timeout_seconds='30'/><exec_methodtype='method'name='stop'exec='/lib/svc/method/newservice stop'timeout_seconds='30'/><property_groupname='startd'type='framework'><propvalname='duration'type='astring'value='transient'/></property_group><instancename='default'enabled='true'/><stabilityvalue='Unstable'/><template><common_name><loctextxml:lang='C'>Newservice
</loctext></common_name></template></service></service_bundle>
svc.configd: smf(5) database integrity check of:
/etc/svc/repository.db
failed. The database might be damaged or a media error might have
prevented it from being verified. Additional information useful to
your service provider is in:
/etc/svc/volatile/db_errors
The system will not be able to boot until you have restored a working
database. svc.startd(1M) will provide a sulogin(1M) prompt for recovery
purposes. The command:
/lib/svc/bin/restore_repository
can be run to restore a backup version of your repository. See
http://sun.com/msg/SMF-8000-MY for more information.
To resolve this issue:
Reboot in failsafe mode (grub)
Fix all filesystem fragmentation issues (wizard)
Mount your root partition in read/write mode in /a (wizard)
The following backups of /etc/svc/repository.db exists, from
oldest to newest:
... list of backups ...
The backups are named based on their type and the time when they were taken.
Backups beginning with "boot" are made before the first change is made to
the repository after system boot. Backups beginning with "manifest_import"
are made after svc:/system/manifest-import:default finishes its processing.
The time of backup is given in YYYYMMDD_HHMMSS format.
Please enter one of:
1) boot, for the most recent post-boot backup
2) manifest_import, for the most recent manifest_import backup.
3) a specific backup repository from the above list
4) -seed-, the initial starting repository. (All customizations
will be lost.)
5) -quit-, to cancel.
Enter response [boot]:
After confirmation, the following steps will be taken:
svc.startd(1M) and svc.configd(1M) will be quiesced, if running.
/etc/svc/repository.db
-- renamed --> /etc/svc/repository.db_old_YYYYMMDD_HHMMSS
/etc/svc/volatile/db_errors
-- copied --> /etc/svc/repository.db_old_YYYYMMDD_HHMMSS_errors
repository_to_restore
-- copied --> /etc/svc/repository.db
and the system will be rebooted with reboot(1M).
Proceed [yes/no]? yes