rcapstat(1M).
On Thu, Aug 21, 2008 at 1:29 AM, Gauss Tang - Sun Microsystems
[EMAIL PROTECTED] wrote:
Dear Expert,
We can check the zone memory allocation via command
zonecfg -z zonename info
capped-memory:
physical: 256M
But how to check this info after longin the zone?
--
--JeffV
Nils Goroll wrote:
I suggest to introduce an additional milestone (e.g. milestone/ready)
with optional dependencies on all system services, roughly matching
the time when rc3 is run.
That's much later than is desirable for these patches. The goal is to
have the system as quiet as possible.
[ Which brain-dead mail client turns all of the spaces in the Subject
into tabs? ]
Zones folks: the current proposed answers to this problem involve
moving system/filesystem/local into milestone/single-user. That was
apparently considered and rejected as the answer for the patchadd
problem
On Thu, Aug 21, 2008 at 12:54:14PM -0700, Jordan Brown wrote:
[ Which brain-dead mail client turns all of the spaces in the Subject
into tabs? ]
Zones folks: the current proposed answers to this problem involve
moving system/filesystem/local into milestone/single-user. That was
Steve Lawrence wrote:
I assume you are targeting this change for s10.
Yes.
The single-user milestone is intended to mimic the traditional unix
run-level 1 (S?)
Nit: Run level 1 is slightly different from S.
This is typically where an admin would run stuff like
fsck (on filesystems that
The list of use cases is really pretty simple:
1) Administrator has in hand a patch that says install in single user
mode. What does this administrator do? The answer seems self-evident:
take the system to single-user mode (either by booting the system in
single-user mode using boot
Steve Lawrence wrote:
A. Make patchadd verify that the system is in single user milestone when
installing a single-user patch.
That's a non-starter. *Many* of our customers ignore our recommendation
to install patches in single-user mode, and will revolt if we attempt to
enforce it.
In
On Thu, Aug 21, 2008 at 04:01:43PM -0700, Jordan Brown wrote:
Steve Lawrence wrote:
A. Make patchadd verify that the system is in single user milestone when
installing a single-user patch.
That's a non-starter. *Many* of our customers ignore our recommendation
to install patches in
