Re: [zones-discuss] s10 brand Phase I webrev

[Jerry Jelinek]

Edward Pilatowicz wrote:

- also, since the s10 brand is derived from the sn1 brand, could you
please ensure that all the new s10 brand that are being created are
derived from the corresponding sn1 brand files?  ie, the s10 brand files
which are derived from sn1 brand files should be created via "hg cp ..."
instead of "cp ...; hg new ..." (this will preserve the sn1 brand
revision history when looking at s10 brand files.)

additionally, danek has an enhanced version of webrev where, if the s10
branded files are "hg cp"d from the sn1 files, we'll just see the deltas
against the sn1 files (instead of having all these files show up as new).


I've generated a new webrev using some improvements Ed made to
webrev.  This, combined with the use of 'hg copy', make the
webrev much smaller and easier to review.  I've uploaded
the new webrev to:

http://cr.opensolaris.org/~gjelinek/webrev.646/

Please get me any comments by the end of the week so that we
have time to make the necessary changes and rerun the tests before
we integrate.

Thanks,
Jerry
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Solaris Zone errors

[Trevor Pretty]

Nicholas Senedzuk wrote:
Sounds like there is a problem writing the to the log file
for the services. I would check you disks and make sure you have none
failing. If you do a svcs -l service_name you it will tell you where
the log file is located.

Or where the service is
trying to write is mounted read only from the global zone.


  On Tue, Sep 29, 2009 at 5:44 AM, Ketan 
wrote:
  after
booting up my zone i get following error

Code:
# zlogin -C DB_zone
[Connected to zone 'DB_zone' console]
Sep 29 09:18:46 svc.startd[5680]: Could not log for
svc:/system/filesystem/root:default: write(51) failed with I/O error.

Sep 29 09:18:47 svc.startd[5680]: Could not log for
svc:/system/installupdates:default: write(17) failed with I/O error.
Sep 29 09:18:47 svc.startd[5680]: Could not log for
svc:/network/physical:default: write(10) failed with I/O error.
Sep 29 09:18:47 svc.startd[5680]: Could not log for
svc:/network/physical:default: write(10) failed with I/O error.
Sep 29 09:18:48 svc.startd[5680]: Could not log for
svc:/system/boot-archive:default: write(10) failed with I/O error.
Sep 29 09:18:49 svc.startd[5680]: Could not log for
svc:/milestone/network:default: write(20) failed with I/O error. what
could be the reason for this ?
--
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org

  
  









www.eagle.co.nz 
This email is confidential and may be legally 
privileged. If received in error please destroy and immediately notify 
us.


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] How to enable a service of a zone that is not running...

[Brad Diggs]

Thanks to everyone that responded!  Of the options presented, I  
believe that the best option that will have the longest

supportability across Solaris and OpenSolaris versions over time is...

"...create an rc script in the zone with the svcadm enable command  
which removes itself after executing the svcadm command."

  - Bernd Schemmer

Thanks again!

Brad
Brad Diggs
Principal Field Technologist



Sun Microsystems, Inc.
Phone x52957/+1 972-992-0002
Mail bradley.di...@sun.com
Blog http://TheZoneManager.com
Blog http://BradDiggs.com

On Sep 28, 2009, at 1:41 PM, Renaud Manus wrote:


It should be possible to do it since the integration of PSARC
2008/015 svccfg refresh subcommand in nevada.

eg.

# svccfg
svc:> repository /etc/svc/repository.db
svc:> select 
svc:> setprop general/enabled = true
svc:> refresh
svc:> exit

I've never tried it though and I'm not sure you can
manipulate the 'general' property group offline.

Btw, to be able to do it, the NGZ must be running the
same OS as the Global Zone otherwise you could corrupt
the repository.

-- Renaud

Bernd Schemmer wrote:

AFAIK the  "upgrade" script is not an stable interface.
IMHO it's better to create an rc script in the zone with the svcadm  
enable command which removes itself after executing the svcadm  
command.

regards
Bernd
Mike Gerdts wrote:
On Sun, Sep 27, 2009 at 10:50 AM, Brad Diggs  
 wrote:


I would like to svcadm enable a service of a non-global zone  
who's state is not 'running'.

Is that possible?  If so, how?
Thanks in advance,
Brad
Brad Diggs
Principal Field Technologist



You can cause it to become enabled on the next boot with:

echo "svcadm enable $fmri" >> $zonepath/root/var/svc/profile/upgrade

This will get processed when manifest-import runs early in the zone
boot process.  I'm not so sure that this is considered to be an
interface, so it may break at any time.  It is probably best to  
ask on

smf-discuss if you care about the stability of this mechanism.

--
Mike Gerdts
http://mgerdts.blogspot.com/
___
zones-discuss mailing list
zones-discuss@opensolaris.org



___
zones-discuss mailing list
zones-discuss@opensolaris.org


___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] updating zones question

[Jerry Jelinek]

Will Fiveash wrote:

As an aside it would  be nice if the pkg image-update command provided
an option to update all zones configured in the BE being updated.


There is no option because it will eventually do that
automatically, just like upgrading s10 today will also
upgrade all zones.  We're just not there yet.

Jerry

___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] Solaris Zone errors

[Nicholas Senedzuk]

Sounds like there is a problem writing the to the log file for the services.
I would check you disks and make sure you have none failing. If you do a
svcs -l service_name you it will tell you where the log file is located.

On Tue, Sep 29, 2009 at 5:44 AM, Ketan  wrote:

> after booting up my zone i get following error
>
> Code:
> # zlogin -C DB_zone
> [Connected to zone 'DB_zone' console]
> Sep 29 09:18:46 svc.startd[5680]: Could not log for
> svc:/system/filesystem/root:default: write(51) failed with I/O error.
>
> Sep 29 09:18:47 svc.startd[5680]: Could not log for
> svc:/system/installupdates:default: write(17) failed with I/O error.
> Sep 29 09:18:47 svc.startd[5680]: Could not log for
> svc:/network/physical:default: write(10) failed with I/O error.
> Sep 29 09:18:47 svc.startd[5680]: Could not log for
> svc:/network/physical:default: write(10) failed with I/O error.
> Sep 29 09:18:48 svc.startd[5680]: Could not log for
> svc:/system/boot-archive:default: write(10) failed with I/O error.
> Sep 29 09:18:49 svc.startd[5680]: Could not log for
> svc:/milestone/network:default: write(20) failed with I/O error. what could
> be the reason for this ?
> --
> This message posted from opensolaris.org
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
>
___
zones-discuss mailing list
zones-discuss@opensolaris.org

[zones-discuss] Solaris Zone errors

[Ketan]

after booting up my zone i get following error 

Code:
# zlogin -C DB_zone
[Connected to zone 'DB_zone' console]
Sep 29 09:18:46 svc.startd[5680]: Could not log for 
svc:/system/filesystem/root:default: write(51) failed with I/O error.

Sep 29 09:18:47 svc.startd[5680]: Could not log for 
svc:/system/installupdates:default: write(17) failed with I/O error.
Sep 29 09:18:47 svc.startd[5680]: Could not log for 
svc:/network/physical:default: write(10) failed with I/O error.
Sep 29 09:18:47 svc.startd[5680]: Could not log for 
svc:/network/physical:default: write(10) failed with I/O error.
Sep 29 09:18:48 svc.startd[5680]: Could not log for 
svc:/system/boot-archive:default: write(10) failed with I/O error.
Sep 29 09:18:49 svc.startd[5680]: Could not log for 
svc:/milestone/network:default: write(20) failed with I/O error. what could be 
the reason for this ?
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org