Prev: Hung process
Next: Xcall
From: Dan Stromberg on 11 Mar 2005 14:26

When I try to, for example, enable NIS client functionality during an
autoinstall script on a Solaris 10 system, I get:

+ chroot /a /usr/sbin/svcadm enable network/nis/client
svcadm: Couldn't bind to svc.configd.

Has someone worked out a good way of enabling such things during an
install?

I imagine I could get around it by creating an rc script that would
enable NIS and then remove itself (the rc script), but is there a better
way?

Would it be reasonable to fire up svc.configd in the chroot environment?

Thanks!

From: Coy Hile on 11 Mar 2005 14:50
Dan Stromberg wrote:
> When I try to, for example, enable NIS client functionality during an
> autoinstall script on a Solaris 10 system, I get:
>
> + chroot /a /usr/sbin/svcadm enable network/nis/client
> svcadm: Couldn't bind to svc.configd.
>
> Has someone worked out a good way of enabling such things during an
> install?
>
> I imagine I could get around it by creating an rc script that would
> enable NIS and then remove itself (the rc script), but is there a better
> way?
>
> Would it be reasonable to fire up svc.configd in the chroot environment?
>

The supported way to do this is to configure a one-time manifest that
runs the first time you boot the system, then disables itself. Model
it after the inet-upgrade service.


--
Coy Hile
hile(a)cse.psu.edu
From: Darren Dunham on 11 Mar 2005 14:57
Dan Stromberg <strombrg(a)dcs.nac.uci.edu> wrote:

> When I try to, for example, enable NIS client functionality during an
> autoinstall script on a Solaris 10 system, I get:

> + chroot /a /usr/sbin/svcadm enable network/nis/client
> svcadm: Couldn't bind to svc.configd.

> Has someone worked out a good way of enabling such things during an
> install?

I think the recommended way to do this is to install a site.xml file
into /var/svc/profile. There you can enable and disable services.

--
Darren Dunham ddunham(a)taos.com
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. >
From: Darren Dunham on 11 Mar 2005 16:55
Coy Hile <hile(a)cse.psu.edu> wrote:
> Dan Stromberg wrote:
>> When I try to, for example, enable NIS client functionality during an
>> autoinstall script on a Solaris 10 system, I get:
>>
>> + chroot /a /usr/sbin/svcadm enable network/nis/client
>> svcadm: Couldn't bind to svc.configd.
>>
>> Has someone worked out a good way of enabling such things during an
>> install?
>>
>> I imagine I could get around it by creating an rc script that would
>> enable NIS and then remove itself (the rc script), but is there a better
>> way?
>>
>> Would it be reasonable to fire up svc.configd in the chroot environment?
>>

> The supported way to do this is to configure a one-time manifest that
> runs the first time you boot the system, then disables itself. Model
> it after the inet-upgrade service.

I think that's a proper method for running general scripts after
jumpstart. But if all you want to do is just mark particular services
as up or down upon first launch, site.xml may be easier. It is applied
the first time it is seen by the system, so you don't have to make it
disable itself.

--
Darren Dunham ddunham(a)taos.com
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. >
 | 
Pages: 1
Prev: Hung process
Next: Xcall