Hi Tom,

Thank you for looking into my machine, and pointing out that the
directory that I thought have build 105 content actually doesn't.
I populated another directory with build 105 content, and ran my
commands, and I do get the warning as expected.

Thanks for your help.

--Karen

Tom Whitten wrote:
> Thanks for giving me access to your machine, Karen.  I don't think that I
> would have been able to figure this out, otherwise.  It doesn't appear as
> if your /dpool/105-content directory actually contains b105 material.  More
> specifically there were a few things that I was able to check from an SMF
> standpoint, and they do not appear to have the extended templates stuff
> that was putback into b102.
>
> I looked at /dpool/105-content/var/svc/manifest/system/svc/restarter.xml,
> and it doesn't have all the templates specifications that we putback into
> b102.  To see what I mean, compare it to
> /var/svc/manifest/system/svc/restarter.xml on your machine.
>
> Also /dpool/105-content/usr/sbin/svccfg appears to the b101 version of
> svccfg.  To make a quick check, I set up the three enviroment variables as
> you did and ran "/dpool/105-content/usr/sbin/svccfg help".  In the output
> of this command the Entity commands were listed as "list select unselect
> add delete".  In b102 and later, svccfg adds "describe" to the end of that
> list.
>
> I hope this helps.  If you find that I've been looking in the wrong place,
> let me know.
>
> tom
>
> Karen Tung writes:
>   
>> Hi,
>>
>> I am trying to import a b105 repository on a snv_b101 machine.
>> I am setting the repository, the commands and everything to a directory 
>> that contain
>> the b105 bits.  Import of all manifests except postrun.xml seem to work OK
>> that way on my snv_b101 system. 
>>
>> I am getting a warning about postrun.xml.
>> Looking at the template defined in restarter.xml, I can see that the 
>> postrun.xml
>> manifest is really missing the stop method.  What I don't understand is 
>> why does
>> it work on a b105 system without the warning.
>>
>> I have narrowed it down to executing the following commands.
>> If I execute the following sequence of commands on a b105 system, 
>> there's no error or warning.
>> But if I execute the same sequence of commands on a b101 system, I got the
>> warning about the postrun.xml.
>>
>> =========================
>> export 
>> SVCCFG_DTD=/dpool/105-content/usr/share/lib/xml/dtd/service_bundle.dtd.1
>> export SVCCFG_REPOSITORY=/dpool/105-content//etc/svc/repository.db
>> export LD_LIBRARY_PATH=/dpool/105-content/lib:/dpool/105-content/usr/lib
>> /dpool/105-content/usr/sbin/svccfg import 
>> /dpool/105-content/var/svc/manifest/system/svc/restarter.xml
>> /dpool/105-content/usr/sbin/svccfg validate 
>> /dpool/105-content/var/svc/manifest/system/postrun.xml
>>
>> ---------
>> Required property group missing: FMRI="svc:/system/postrun:default"; 
>> Name of missing property group="stop"; Type of missing property 
>> group="method"; Template source="svc:/system/svc/restarter:default"; 
>> pg_pattern name="stop"; pg_pattern type="method"
>> svccfg: Validation failed.
>> ---------
>>
>> ===========================
>>
>> I couldn't figure out why I don't get the warning on a b105 system.
>> Any idea on what else I need to set up on my build 101 system to not get 
>> the warning?
>>
>> Thanks,
>>
>> --Karen
>>
>> _______________________________________________
>> smf-discuss mailing list
>> smf-discuss at opensolaris.org
>>     


Reply via email to