Is the /etc/system file read in Solaris 10 non global zones

On 11/01/12 09:55, Dariusz Dolecki wrote:

Probably not.  The file is used for kernel settings and there is only
one kernel on a Solaris system.

What do you want to change in a zone that you can't change in the zone's
configuration?

--
Ian Collins

In article <afdk2cFh7l...@mid.individual.net>,
Ian Collins  <ian-n...@hotmail.com> wrote:

S10 kernel patches require its presence even when running within
a zone.
The hack for a S10 system p2v migrated was touch /etc/system.
Never debugged why the p2v tool didn't include the file.

John
groenv...@acm.org

On Oct 31, 2:55 pm, Dariusz Dolecki <dariusz.dole...@gmail.com> wrote:

I'm not that great with zones but I agree with Ian that since there is
only
one kernel, you would want only one /etc/system in the global zone.

If you want to apply resource controls to a non-global zone in
the Solaris 10 release, see this doc:

http://docs.oracle.com/cd/E18752_01/html/817-1592/z.config.ov-3.html

particularly, this section, Setting Zone-Wide Resource Controls

Thanks, Cindy

On 11/01/12 10:47, John D Groenveld wrote:

I've never had to do that and I have a number of legacy Solaris 10
machines now running as zones on Solaris 11.  Looking in one, the
original /etc/system is present.

--
Ian Collins

No.  Note that many of the resource controls which used to be set in
/etc/system can be set in a different way (specifically System V IPC &
shared memory).

The rest is all global such as how many groups you can be in or whether the
stack is executable or not.

Casper

In article <k6s68r$oo4...@tr22n12.aset.psu.edu>,
John D Groenveld <groen...@cse.psu.edu> wrote:

That may explain why 147440-25 installed normally in the global zone,
but was rejected for the non-global (which apparently are now called
"local") zones.  Up through 147440-23 (I skipped -24) kernel patches
were always installed even in non-global zones without /etc/system.

                             :: Jeff Makey
                                j...@sdsc.edu

Department of Tautological Pleonasms and Superfluous Redundancies Department

The S10 KJP tries to perform some lofi(1M) magic with system(4)
and falls off the stage when it doesn't exist.
See <jfm9na$gs3...@tr22n12.aset.psu.edu>

John
groenv...@acm.org

Creating an empty /etc/system file in the non-global zone made no
difference for me.  147440-25 (from -23) still insists upon installing
itself only in the global zone.  Is it just me?

                             :: Jeff Makey
                                j...@sdsc.edu

Department of Tautological Pleonasms and Superfluous Redundancies Department

Oracle bug #15826883 indicates that patch 119254-87 is the culprit in
my observed failure to apply 147440-25 to non-global zones.  Oracle
knowledge base article ID 1504460.1 (Solaris 10 Patches May Fail to
Install in Non-global Zones) has their official word on this problem.

Anyone who installs patches in the order that they were released would
install 147440-25 *before* 119254-87 and not see the problem that I
got by installing 119254-87 first, and simply backing out 119254-87
should be sufficient for them.  I have done this on hosts that have no
non-global zones.

The recovery process for my hosts that do have non-global zones is to
first patchrm 147440-25, then patchrm 119254-87, reboot (may not
strictly be necessary), patchadd 147440-25, and reboot again to make
147440-25 take effect.  In this case it is important to remove
147440-25 before 119254-87 (the reverse order that they were
installed).

Both 119254-87 and 119255-87 have been withdrawn, so that should help
save everyone else from encountering this difficulty in the future.

                             :: Jeff Makey
                                j...@sdsc.edu

Department of Tautological Pleonasms and Superfluous Redundancies Department

/etc/system file is for setting kernel parameters.
Solaris shares its kernel to all zones
So there will not be any /etc/system file in a non-global zone