Mike Gerdts wrote:
> On Mon, Aug 11, 2008 at 8:35 AM, Glenn Brunette <[EMAIL PROTECTED]> wrote:
>> My apologies if this is a RTFM moment, but I have been looking and have
>> been unable to find an answer. If memory caps are defined for a given
>> zone, why doesn't the output of swap display the
On Mon, Aug 11, 2008 at 8:35 AM, Glenn Brunette <[EMAIL PROTECTED]> wrote:
>
> My apologies if this is a RTFM moment, but I have been looking and have
> been unable to find an answer. If memory caps are defined for a given
> zone, why doesn't the output of swap display the cap?
>
> # zonecfg -z we
Thanks!
Jerry Jelinek wrote:
> Glenn Brunette wrote:
>> My apologies if this is a RTFM moment, but I have been looking and have
>> been unable to find an answer. If memory caps are defined for a given
>> zone, why doesn't the output of swap display the cap?
>
> 6572077 size of swapfs filesystem
Glenn Brunette wrote:
> My apologies if this is a RTFM moment, but I have been looking and have
> been unable to find an answer. If memory caps are defined for a given
> zone, why doesn't the output of swap display the cap?
6572077 size of swapfs filesystems in a zone should reflect zone.max-swap
My apologies if this is a RTFM moment, but I have been looking and have
been unable to find an answer. If memory caps are defined for a given
zone, why doesn't the output of swap display the cap?
# zonecfg -z web info capped-memory
capped-memory:
physical: 1G
[swap: 200M]
# zon