Very Computer

In the past, to disable services and init scripts during a Jumpstart
build, one would just have to include a simple line in the finish
scripts such as:

mv -f /a/etc/rc2.d/S71rpc /a/etc/rc2.d/s71rpc

etc, etc.

With Solaris 10, many (but yes, not all) of what was in the rc
directories have been moved into the Service Management Facility which
is administered with svcadm(1M).

I'd like to continue to disable services via the finish script, but as I
sit down to fashion one for Solaris 10, I realize that it's not as
straight-forward as it used to be. For instance, how does one tell
svcadm to distinguish between the jumpstart miniroot and the
installation you really want to act on, which is mounted on /a ?

I'd like to stick to using svcadm(1M) for doing this, but if it means
mucking around in some directory under /a, then so be it.

Any ideas?

/dale

Sami

--
  .signature: no such file or directory

--
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

/dale

When it first boots, it'll import that file and act on it.

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

  <service name='network/finger' version='1' type='service'>
    <instance name='default' enabled='false'/>
  </service>

to disable this one service ?

My problem is that until now I'm using a set of scripts (which get
called by the finish script) each one doing all things required to modify
the behaviour of a single service. Like a sendmail script which modifies
sendmail.cf and installs /etc/default/sendmail, or a dtlogin-disable
script which disables dtlogin. That's more flexible than one
big script (I think JASS works the same way). Unfortunately having
to install a site.xml which modifies a lot of services would break
this setup, and I'd like to find the best workaround within SMF.

mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

I think you need more xml gunk like the "generic.xml" and such files.

Quote:>My problem is that until now I'm using a set of scripts (which get
>called by the finish script) each one doing all things required to modify
>the behaviour of a single service. Like a sendmail script which modifies
>sendmail.cf and installs /etc/default/sendmail, or a dtlogin-disable
>script which disables dtlogin. That's more flexible than one
>big script (I think JASS works the same way). Unfortunately having
>to install a site.xml which modifies a lot of services would break
>this setup, and I'd like to find the best workaround within SMF.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

The only thing you'd need to add to the example above is the
service_bundle tag to wrap all of the service declarations.

Quote:> My problem is that until now I'm using a set of scripts (which get
> called by the finish script) each one doing all things required to modify
> the behaviour of a single service. Like a sendmail script which modifies
> sendmail.cf and installs /etc/default/sendmail, or a dtlogin-disable
> script which disables dtlogin. That's more flexible than one
> big script (I think JASS works the same way). Unfortunately having
> to install a site.xml which modifies a lot of services would break
> this setup, and I'd like to find the best workaround within SMF.

Dave

  <service_bundle type='profile' name='default'>
   <service name='network/finger' version='1' type='service'>
    <instance name='default' enabled='false'/>
   </service>
  </service_bundle>

and then "echo >>" a line like this into /a/var/svc/profile/site.xml:

  <xi:include href='file:/var/svc/profile/disable_finger.xml' />

Any other <service>_disable or <service>_modify script could then
do the same without interfering with other services ? That'd be
a viable solution, at least.

The obvious RFE is of course that the SMF configuration commands
(svcadm, inetadm) should support an option or mode to enable/disable/
modify services when running under jumpstart. That would make life
much easier.

mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

Quote:> The obvious RFE is of course that the SMF configuration commands
> (svcadm, inetadm) should support an option or mode to enable/disable/
> modify services when running under jumpstart. That would make life
> much easier.

Dave