Thursday, November 30, 2006

Resource Management resources

I've been looking at documentation on Resource Management over the last few days. Here are some of the articles that I have found. Unfortunately, much of the information I found is based on the Solaris 9 and even Solaris 8 implementations of Resource Manager, which is only somewhat useful when looking at Solaris 10.

If you are aware of additional resources, please feel free to add them to the comments on this post.

Here are the best items I've found:

System Administration Guide: Solaris Containers-Resource Management and Solaris Zones from the Solaris 10 documentation. This is quite well-written, though organized differently than I would have done it.

The Sun BluePrints Guide to Solaris Containers by Foxwell, Lageman, Hoogeveen, Rozenfeld, Setty and Victor. The Resource Management section is also quite well-written, and I found the organization to be more helpful than the manual in the Solaris 10 docs.

Solaris Resource Management by Galvin in SysAdmin. This is a high-level introduction. Though it is specific to Solaris 9, it is still the best quick introduction to the subject I've come across.

Capping a Solaris processes memory by matty is a blog page describing the ability of Solaris 10 to use rcapd to manage memory. This is a brief but thorough discussion of this topic.

Wednesday, November 29, 2006


This blog is designed to be a companion to my Solaris Troubleshooting web site, hosted by Princeton University.

I used to have an email link to solicit feedback on the web site. I received some outstanding feedback, but I also received an outstanding amount of spam.

I am in the process of updating the site to include more Solaris 10 specific information, especially with regards to Resource Management and dtrace. I've posted a first cut at a Resource Management page.

Thanks to everyone who contributed to the old Solaris 8 site, and a special thanks to Princeton University for continuing to host the site long after I no longer worked on their Unix team.

--Scott Cromar