I've been restricting /tmp in subzones by adding the option 'size=2048m'
to the /tmp entry in /etc/vfstab.
By default, there are two other tmpfs partitions mounted on the system,
/var/run and /etc/svc/volatile. These aren't as important as /tmp since
by default they are permed 755 while /tmp is permed 1777.
I noticed that if an entry for /var/run is added to /etc/vfstab, then its
size can be restricted as well, however, this doesn't work for
/etc/svc/volatile. Where can i set a limit on the size of
/etc/svc/volatile?
I also noticed that root can mount any other tmpfs filesystems in
subzones, without a limit on the amount of virtual memory it will take up.
Is it possible to limit this behaviour?
In a more general sense, what's the proper way to limit the amount of
memory (both real and virtual) that a subzone can consume? I understand
that rcapd can be used to (asynchronously) cap the amount of real memory a
project is allowed, but can't root escape this? Is it possible to
restrict the amount of memory root in a subzone can use?
I know there are strong lwp and cpu restrictions that can be enforced, and
i've already set up psets and pools, and restricted zone.max-lwps and
zone.cpu-shares for my subzones. But what about general restrictions for
a zone's memory use?
I've read through http://docs.sun.com/app/docs/doc/817-1592 but perhaps
i've missed a solution or misunderstood this issue. Any pointers would
be welcome.
Thanks,
-f
http://www.blackant.net/
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users
