Hi,

my jumpstart servers usually copy a "S99zzz" onto the client to 
/etc/rc2.d - this script runs after the installation reboot, makes some 
post-installation things and then deletes itself.

On Solaris9, this works great. On my Solaris 10 jumpstart, the script 
isn't executed, although ownerships, rights etc. are correct. Even in 
svcs -a on the machine, I can see:

legacy_run     16:23:00 lrc:/etc/rc2_d/S99zzz

Any ideas why this isn't executed?

Regards,
Dietmar

Dietmar Braun <spam-2009-01-26@arath.org> writes:

>Hi,

>my jumpstart servers usually copy a "S99zzz" onto the client to 
>/etc/rc2.d - this script runs after the installation reboot, makes some 
>post-installation things and then deletes itself.

>On Solaris9, this works great. On my Solaris 10 jumpstart, the script 
>isn't executed, although ownerships, rights etc. are correct. Even in 
>svcs -a on the machine, I can see:

>legacy_run     16:23:00 lrc:/etc/rc2_d/S99zzz

>Any ideas why this isn't executed?

It is executed; why do you think it is not executed?

Have you looked at the log?

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.

In Artikel <4b962795$0$22903$e4fe514c@news.xs4all.nl> schrub 
Casper.Dik@Sun.COM:
> It is executed; why do you think it is not executed?

There are some "echo" statements, which don't appear on the console. 
Also, the rest of the commands is not executed.

Dietmar

Dietmar Braun <spam-2009-01-26@arath.org> writes:

>In Artikel <4b962795$0$22903$e4fe514c@news.xs4all.nl> schrub 
>Casper.Dik@Sun.COM:
>> It is executed; why do you think it is not executed?

>There are some "echo" statements, which don't appear on the console. 
>Also, the rest of the commands is not executed.

The output is not printed on the console.

Check the log files:

/var/svc/log/milestone-multi-user-server:default.log  (rc3.d scripts)
/var/svc/log/milestone-multi-user:default.log	      (rc2.d scripts_

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.

In Artikel <4b963831$0$22936$e4fe514c@news.xs4all.nl> schrub 
Casper.Dik@Sun.COM:
> The output is not printed on the console.

Oh...

> /var/svc/log/milestone-multi-user-server:default.log  (rc3.d scripts)
> /var/svc/log/milestone-multi-user:default.log	      (rc2.d scripts_

Ok, thank you... So what would be the best way to bring it to the 
console? Would be important since I have some interaction in the 
script...

Thank you!
Dietmar

Dietmar Braun <spam-2009-01-26@arath.org> writes:

>In Artikel <4b963831$0$22936$e4fe514c@news.xs4all.nl> schrub 
>Casper.Dik@Sun.COM:
>> The output is not printed on the console.

>Oh...

>> /var/svc/log/milestone-multi-user-server:default.log  (rc3.d scripts)
>> /var/svc/log/milestone-multi-user:default.log	      (rc2.d scripts_

>Ok, thank you... So what would be the best way to bring it to the 
>console? Would be important since I have some interaction in the 
>script...

Ah, with interaction?  You will need to redirect the output to
the physical console:

Something like this:

exec >/dev/msglog 2<>/dev/msglog </dev/console

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.