SMF will not recognize a file that doesn't end in .xml even if the file
data is correct.
zoneadm now enforces that the profile must end in .xml so that if a profile
is given it won't be silently ignored by SMF.
Susan
On 02/ 9/12 02:22 PM, Virginia Wray wrote:
On 02/ 9/12 02:19 PM, Will Fiveash wrote:
On Thu, Feb 09, 2012 at 01:27:34PM -0700, Virginia Wray wrote:
On 02/ 9/12 12:47 PM, Will Fiveash wrote:
# zlogin mit /usr/sbin/sysconfig configure -g system -c
/var/tmp/mit.profile.xml
svcadm: No such instance "svc:/system/svc/restarter:default".
The problem is that you booted the zone and then ran the sysconfig
command. On first boot of the zone, the sysconfig utility is
automatically invoked for an interactive configuration. The system
isn't completely on line, which I think accounts for the svcadm error.
You are, in effect, trying to run sysconfig when it is already
running.
OK, that makes sense. I can see now in the solaris.5 man page that I
can use either zoneadm "clone -c profile.xml" or "install -c
profile.xml" to apply the sysconfig profile data properly.
As an aside, it seems bogus to me that sysconfig requires the profile
file end in .xml. Wouldn't it be better if it made sure the first
non-blank line in the profile file was:
<!DOCTYPE service_bundle SYSTEM
"/usr/share/lib/xml/dtd/service_bundle.dtd.1">
?
Possibly. I'm not sure why the .xml extension was made the requirement.
I'll ask someone who was part of that decision and see if there was a
reason.
ginnie
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org
