Solaris

Hi

I have been told to migrate linux init scripts to solaris 10. i am reading about the chkconfig & SMF ( I came to know that SMF is used in Sol 10 for service management ). The only thing i could not find out ( Because i dont have root access ) is how the links are created in rcX.d directory?

I will try to explain what i understood from different article i found on net

1) there are different run levels generally 0-6 & S/s
2) Default is run level 3
3) with chkconfig user can create links in /etc/rcX.d
4) these links are hard links to files in init.d
5) when server boots up ( assume in run level 3 ) it executes all the scripts whose name starts with "S" under /etc/rc3.d
6) changing that initial letter to something else will skip that test being executed at start

please correct me if what i understood is wrong.

so my question was just by specifying something like in script will create a link under rc3.d dir ?

Code:

#!/bin/sh
# chkconfig: 3 20 20 
# description: blah blah

or do i have to write a script which will create a link in rcX.d folder to this files ?

SMF does not used the /etc/rc?.d/ directories we know and love, it has a set of mlestones, e.g. single-user and multi-user that replicate the run levels. To dictate the order that the services are started in (some may start in parallel) each service has dependencies, e.g. the DNS client will only start once networking has been established and local mounts have been made, a service can also have dependents, e.g. don't allow dtlogin to start until I (e.g. LDAP) am running, these can be listed by running:

Code:

# svcs -d  <servicename>

and

Code:

# svcs -D <servicename>

To see the state of all the services you may run:

Code:

# svcs -a

and to see what have failed you may run:

Code:

# svcs -xv

To start a service you can run:

Code:

# svcadm enable <servicename>

and to stop it you can run:

Code:

# svcadm disable <servicename>

A "-t" parameter makes the change of state temporary (the service will restart on the next reboot rather than staying enabled/disabled) and the "-r" parameter ensures that when starting a service that requires dependencies that they are all started also.

The services are defined using xml files and call scripts very like those that used to appear in /etc/init.d but can also ensure that if a daemon stops running that it gets restarted.

See:
BigAdmin Topic: Solaris Service Management Facility - Quickstart Guide
and:
http://docs.sun.com/app/docs/doc/819...%29#See%20Also


Concerning what you have said:

1. The default run level on a machine that uses the rc scripts is changeable and for a Linux type machine it is 3 for a machine that does not require a GUI (e.g. a web or database server) and is 5 for machine that does (usually desktop machines). The default run level is defined in the /etc/inittab file.

2. Solaris machines (pre SMF) run through all the scripts from rcS.d to rc3.d (or higher), Linux machines (well RedHat anyway) run only those scripts in the default run level's directory which is why you will see links for some services in rc1.d, rc2.d and rc3.d. The S* scripts are run on boot up and the K* scripts on shutdown, changing the S or K to s or k will cause those scripts to be not run.

3. The rc?.d links are usually created by the package or manually on a Solaris system, unlike Linux where chkconfig looks for the chkconfig line in the /etc/init.d script to tell it what links to create for you.

4. The script header you show will cause chkconfig to create S20* and K20* links in the /etc/rc3.d directory only for the service you have installed into /etc/init.d when you run:

Code:

# chkconfig --add <servicename>

Where <servicename> is the name of the script you have installed into /etc/init.d on a Lnux machine but not on a Solaris machine.

HTH

Just a couple of comments/clarifications:
This is however distribution dependent. i.e. slackware uses run level 4 instead of 5 for GUI. Gentoo, Debian, Ubuntu make no distinction between run levels 2,3,4 and 5.
Post SMF Solaris machines also run the rcS.d, rc2.d and rc3.d scripts, a.k.a. legacy startup scripts. Converting startup scripts to smf, while recommended for obvious reasons isn't mandatory.

jlliagre,

1. Thanks for the clarification on other flavors of Linux.

2. Yes, I neglected to mention that rc scripts still work under Solaris 10 and that "svcs -a" lists them as legacy objects, this enables software intended for earlier versions of Solaris that install rc scripts to still work under Solaris 10.

@TonyFullerMalv

thanks for your reply. i am now thinking of using rcX.d scripts ( because in our org other scripts are implemented that way !! )

i thought of creating new thread for some of my questions then i thought why not put it here only

1 ) i have started migrating scripts from linux to solaris i am going through scripts and i found that all init script uses

Code:

. /etc/init.d/functions

which is not there in Solaris!! so what is the solution ? write my own script which with required functions ?

2) In init scripts empty file is created under /var/lock/subsys to avoid duplicate start. how this is implemented in solaris ? i tried searching but couldnt find any useful information.

you can redirect me to some relevant website i will do the rest

Dare I suggest you simply take a copy of the /etc/init.d/functions script and translate any minor changes required to make it Solaris compatible?
Do your scripts actually use any of the functions?

so are you only planning to run legacy scripts or are you going to let SMF manage it? I couldn't find it anywhere in the thread.