Sponsored Content
Full Discussion: Change run level at boot
Operating Systems Solaris Change run level at boot Post 303026868 by gull04 on Tuesday 4th of December 2018 08:31:31 AM
Old 12-04-2018
Hi,

You need to change the smf man 5 smf to take the system to;

milestone/multi-user:default

Instead of;

milestone/multi-user-server:default

Or you can just use svcadm for a temporary change or svccfg to make the change persist.

Regards

Gull04
These 3 Users Gave Thanks to gull04 For This Post:
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Find run-level in solaris 8.

When the solaris 8 have come up, which command can find out the current run-level? thanks. (2 Replies)
Discussion started by: nianzhe
2 Replies

2. Solaris

Confusion In run level...

Dear Friends..!! i am quit confused about the SOLARIES RUN level that is 0 . 1 or s S ... please let me know the diffirence between these run level ... 0,1 and s S... have a great day Uday naikwadi (1 Reply)
Discussion started by: udayn
1 Replies

3. SuSE

Run Level Services file

Hello, I recently updated a test system from Suse 8 to 9.3. Now our runlevel services program doesn't work, but works fine on our other 9.3 boxes. We have a file in /etc/init.d/rc3.d called S99fooprog(not actual name ofcourse). It just has a command to start a program daemon up. Anyways... (3 Replies)
Discussion started by: benefactr
3 Replies

4. Solaris

Run Level 1, S and small s

Hi Experts, A stupid question for experts :confused: !! What is the difference between run level ‘1', runlevel ‘S' and small ‘s'. As per my understanding the difference between S and 1 is that in case of ‘S' it only going to mount the critical file system which ideal should be... (2 Replies)
Discussion started by: kumarmani
2 Replies

5. Solaris

How to get the initdefault run level in Solaris 10

Hi All, In Solaris 9 and below I will get the init run-level by checking the /etc/inittab entry is:3:initdefault: But in Solaris 10 we are using the smf functionality. Here how I can get the init default run level. Please help me in this problem. Regards, ... (2 Replies)
Discussion started by: kalpeer
2 Replies

6. Solaris

Difference between run level & init level

what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies

7. UNIX for Dummies Questions & Answers

When the run level is changed from 5 to 3?

A Bourne Shell script is placed in /etc/rc.d/rc3.d called S57apache. What will happen with this script when the run level is changed from 5 to 3? many thanks (4 Replies)
Discussion started by: lemon_06
4 Replies

8. Solaris

Solaris 10 - Run Level Modification

Hello, I'm creating a VM Image of Solaris 10 on VM Player. I've completed the installation & I am using the Java Desktop as my default logon. I need to modify the Run Level to Console Mode (permanently). Unlike previous versions or Linux, modifying inittab file is not an option here. Please... (2 Replies)
Discussion started by: DevendraG
2 Replies

9. Shell Programming and Scripting

Perl - what run level

Is there a way to tell what runlevel is currently being used, for example is a user is using the gui or is the have pressed Alt+Ctrl+F1 to drop to the terminal?? (3 Replies)
Discussion started by: ab52
3 Replies

10. UNIX for Dummies Questions & Answers

Network monitoring at boot level.

Whenever i start my server it takes app 2 minutes to get into network (After starting the network service on boot). I inquire the network guys for possible causes but they say it will need both side monitoring . One is switch side and the second is server side. I m not sure how do i check... (6 Replies)
Discussion started by: pinga123
6 Replies
svcadm(1M)						  System Administration Commands						svcadm(1M)

NAME
svcadm - manipulate service instances SYNOPSIS
/usr/sbin/svcadm [-v] enable [-rst] {FMRI | pattern}... /usr/sbin/svcadm [-v] disable [-st] {FMRI | pattern}... /usr/sbin/svcadm [-v] restart {FMRI | pattern}... /usr/sbin/svcadm [-v] refresh {FMRI | pattern}... /usr/sbin/svcadm [-v] clear {FMRI | pattern}... /usr/sbin/svcadm [-v] mark [-It] instance_state {FMRI | pattern}... /usr/sbin/svcadm [-v] milestone [-d] milestone_FMRI DESCRIPTION
svcadm issues requests for actions on services executing within the service management facility (see smf(5)). Actions for a service are carried out by its assigned service restarter agent. The default service restarter is svc.startd (see svc.startd(1M)). OPTIONS
The following options are supported: -v Print actions verbosely to standard output. SUBCOMMANDS
Common Operations The subcommands listed below are used during the typical administration of a service instance. For subcommands taking one or more operands, if the operand specifies a service (instead of a service instance), and that service has only a single instance, svcadm operates on that instance. If an abbreviated FMRI (a fault management resource identifier) or pattern matches more than one service, a warning message is displayed and that operand is ignored. See smf(5). In the case that the service has more than one instance, svcadm return a non-zero exit status. enable [-rst] {FMRI | pattern}. . . Enables the service instances specified by the operands. For each service instance, the assigned restarter will try to bring it to the online state. This action requires permission to modify the "general" property group of the service instance (see smf_security(5)). If the -r option is specified, svcadm enables each service instance and recursively enables its dependencies. If the -s option is specified, svcadm enables each service instance and then waits for each service instance to enter the online or degraded state. svcadm will return early if it determines that the service cannot reach these states without administrator interven- tion. If the -t option is specified, svcadm temporarily enables each service instance. Temporary enable only lasts until reboot. This action requires permission to modify the "restarter_actions" property group of the service instance (see smf_security(5)). By default, enable is persistent across reboot. disable [-st] {FMRI | pattern}. . . Disables the service instance specified by the operands. For each service instance, the assigned restarter will try to bring it to the disabled state. This action requires permission to modify the "general" property group of the service instance (see smf_security(5)). If the -s option is specified, svcadm disables each service instance and then waits for each service instance to enter the disabled state. svcadm will return early if it determines that the service cannot reach this state without administrator intervention. If the -t option is specified, svcadm temporarily disables each service instance. Temporary disable only lasts until reboot. This action requires permission to modify the "restarter_actions" property group of the service instance (see smf_security(5)). By default, disable is persistent across reboot. restart {FMRI | pattern}. . . Requests that the service instances specified by the operands be restarted. This action requires permission to modify the "restarter_actions" property group of the service instance (see smf_security(5)). This subcommand can restart only those services that are in the online or degraded states, as those states are defined in smf(5). refresh {FMRI | pattern}. . . For each service instance specified by the operands, requests that the assigned restarter update the service's running configuration snapshot with the values from the current configuration. Some of these values take effect immediately (for example, dependency changes). Other values do not take effect until the next service restart. See the restarter and service documentation for more informa- tion. If the service is managed by svc.startd(1M), the refresh method will be invoked if it exists to request the service reread its own con- figuration. For other restarters, see the restarter documentation. This action requires permission to modify the "restarter_actions" property group of the service instance (see smf_security(5)). clear {FMRI | pattern}. . . For each service instance specified by the operands, if the instance is in the maintenance state, signal to the assigned restarter that the service has been repaired. If the instance is in the degraded state, request that the assigned restarter take the service to the online state. This action requires permission to modify the "restarter_actions" property group of the service instance (see smf_secu- rity(5)). Exceptional Operations The following subcommands are used for service development and temporary administrative manipulation. mark [-It] instance_state {FMRI | pattern}. . . If instance_state is "maintenance", then for each service specified by the operands, svcadm requests that the assigned restarter place the service in the maintenance state. See svc.startd(1M) and inetd(1M) for a detailed description of the actions taken for each restarter. If instance_state is "degraded", then for services specified by the operands in the online state, svcadm requests that the restarters assigned to the services move them into the degraded state. If the -I option is specified, the request is flagged as immediate. The -t option is only valid for maintenance requests. When this option is specified, the request is flagged as temporary, and its effect will only last until the next reboot. milestone [-d] milestone_FMRI If milestone_FMRI is the keyword "none", all services other than the master restarter, svc:/system/svc/restarter:default, will be tem- porarily disabled. If milestone_FMRI is the keyword "all", temporary enable and disable requests for all services will be nullified. If milestone_FMRI is one of the following: svc:/milestone/single-user:default svc:/milestone/multi-user:default svc:/milestone/multi-user-server:default then temporary enable and disable requests for the indicated service and all services it depends on (directly or indirectly) will be nullified. All other services will be temporarily disabled. Changing the system's current milestone with the "milestone" subcommand will not change the current run level of the system. To change the system's run level, invoke /sbin/init directly. This action requires permission to modify the "options_ovr" property group of the svc:/system/svc/restarter:default service instance (see smf_security(5)). The -d option immediately changes the milestone to the requested milestone, as above. Additionally, it makes the specified milestone the default boot milestone, which persists across reboot. The default milestone is defined by the options/milestone property on the master restarter, svc:/system/svc/restarter:default. If this property is absent, "all" is the default. This action requires permission to modify the "options" property group of the svc:/system/svc/restarter:default service instance (see smf_security(5)). Operands The following operands are supported: FMRI An FMRI that specifies one or more instances. FMRIs can be abbreviated by specifying the instance name, or the trailing portion of the service name. For example, given the FMRI: svc:/network/smtp:sendmail All the following are valid abbreviations: sendmail :sendmail smtp smtp:sendmail network/smtp While the following are invalid: mail network network/smt If the FMRI specifies a service, then the command applies to all instances of that service. Abbreviated forms of FMRIs are unstable, and should not be used in scripts or other permanent tools. pattern A pattern that is matched against the FMRIs of service instances according to the "globbing" rules described by fnmatch(5). If the pattern does not begin with "svc:", then "svc:/" is prepended. If an abbreviated FMRI or pattern matches more than one service, a warning message is displayed and that operand is ignored. EXAMPLES
Example 1 Restarting a Service Instance The following command restarts the NFS server. The full FMRI for the default service instance is: svc:/network/nfs/server:default However, you can abbreviate the full FMRI as follows: # svcadm restart nfs/server Example 2 Disabling the Standard HTTP Server The following command disables the standard HTTP server, using an abbreviated FMRI: $ svcadm disable http Example 3 Enabling an Instance and Its Dependent Instances The following command enables the foo:bar instance, and all instances on which it depends: $ svcadm enable -r foo:bar Example 4 Synchronously enabling an instance The following command enables the foo:bar instance. The command will not return until the instance comes online or svcadm determines it is not possible for the service to come online. $ svcadm enable -s foo:bar Example 5 Restricting and Restoring the Running Services The following command restricts the running services to single user mode: # svcadm milestone milestone/single-user The following command restores the running services: # svcadm milestone all EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 A fatal error occurred. One or more error messages are displayed on standard error. 2 Invalid command line options were specified. 3 svcadm determined that a service instance that it was waiting for could not reach the desired state without administrator intervention due to a problem with the service instance itself. 4 svcadm determined that a service instance that it was waiting for could not reach the desired state without administrator intervention due to a problem with the service's dependencies. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |See below. | +-----------------------------+-----------------------------+ The interactive output is Uncommitted. The invocation and non-interactive output are Committed. SEE ALSO
svcprop(1), svcs(1), inetd(1M), init(1M), svccfg(1M), svc.startd(1M), libscf(3LIB), contract(4), attributes(5), smf(5), smf_security(5) NOTES
The amount of time svcadm will spend waiting for services and their dependencies to change state is implicitly limited by their method timeouts. For example, a service using the default restarter whose start method hangs will be transitioned to the maintenance state when its timeout expires. svcadm will then consider it impossible for this service to come online without administrator intervention. Attempts to synchronously enable a service which depends (directly or indirectly) on a file may fail with an exit status indicating that dependencies are unsatisfied if the caller does not have the privileges necessary to search the directory containing the file. This limita- tion may be removed in a future Solaris release. SunOS 5.11 9 May 2008 svcadm(1M)
All times are GMT -4. The time now is 03:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy