<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>littleforest &#187; UNIX</title>
	<atom:link href="http://www.littleforest.co.uk/category/unix/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.littleforest.co.uk</link>
	<description>The littleforest Weblog</description>
	<lastBuildDate>Fri, 05 Nov 2010 08:01:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to tell virtual memory on Solaris</title>
		<link>http://www.littleforest.co.uk/unix/how-to-tell-virtual-memory-on-solaris/</link>
		<comments>http://www.littleforest.co.uk/unix/how-to-tell-virtual-memory-on-solaris/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 14:34:18 +0000</pubDate>
		<dc:creator>Gavin Colborne</dc:creator>
				<category><![CDATA[UNIX]]></category>

		<guid isPermaLink="false">http://www.littleforest.co.uk/?p=196</guid>
		<description><![CDATA[Problem
You want to know how much Virtual Memory is available on your Solaris server.
Solution
You simply need to run the command &#8220;ulimit -a&#8221;.
This should output something like the below,  in this you can see the reference to the Virtual Memory.

core file size (blocks)     unlimited
data seg size (kbytes)      [...]]]></description>
		<wfw:commentRss>http://www.littleforest.co.uk/unix/how-to-tell-virtual-memory-on-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Propagating Workarea Group Permissions to Nested Folders &amp; Files on Unix/Linux</title>
		<link>http://www.littleforest.co.uk/teamsite/propagate-wrkarea-grp_perm-unix_linux/</link>
		<comments>http://www.littleforest.co.uk/teamsite/propagate-wrkarea-grp_perm-unix_linux/#comments</comments>
		<pubDate>Thu, 11 Dec 2008 17:23:30 +0000</pubDate>
		<dc:creator>Yusuf Ali</dc:creator>
				<category><![CDATA[TeamSite]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[Yusuf Ali]]></category>

		<guid isPermaLink="false">http://www.littleforest.co.uk/?p=159</guid>
		<description><![CDATA[A problem with TeamSite 6.7.1 on Solaris or Linux servers are when creating a new workarea, group permissions fail to propagate down; meaning permissions don;t filter down.
Any additional folders or files created or imported with the &#8220;File Import&#8221; menu action will take on the logged-on user&#8217;&#8217;s primary group; not the workarea group.
Solution:
To overcome this potential [...]]]></description>
		<wfw:commentRss>http://www.littleforest.co.uk/teamsite/propagate-wrkarea-grp_perm-unix_linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Installation Tips</title>
		<link>http://www.littleforest.co.uk/teamsite/installation-tips/</link>
		<comments>http://www.littleforest.co.uk/teamsite/installation-tips/#comments</comments>
		<pubDate>Wed, 03 Dec 2008 16:54:32 +0000</pubDate>
		<dc:creator>Yusuf Ali</dc:creator>
				<category><![CDATA[Installations]]></category>
		<category><![CDATA[LiveSite]]></category>
		<category><![CDATA[OpenDeploy]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[TeamSite]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[Yusuf Ali]]></category>

		<guid isPermaLink="false">http://www.littleforest.co.uk/?p=151</guid>
		<description><![CDATA[From my experience there are a few things to bear in mind when installing Interwoven Software.  These include

Always install your software as administrator or full root (for solaris/Linux).  In respects to root access it must be full root not any sppof such as sudo. At the lease su root would be acceptable.  There have been [...]]]></description>
		<wfw:commentRss>http://www.littleforest.co.uk/teamsite/installation-tips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Find the number of bytes per inode on Solaris</title>
		<link>http://www.littleforest.co.uk/unix/how-to-find-the-number-of-bytes-per-inode-on-solaris/</link>
		<comments>http://www.littleforest.co.uk/unix/how-to-find-the-number-of-bytes-per-inode-on-solaris/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 08:10:34 +0000</pubDate>
		<dc:creator>Gavin Colborne</dc:creator>
				<category><![CDATA[UNIX]]></category>

		<guid isPermaLink="false">http://www.littleforest.co.uk/stream/?p=44</guid>
		<description><![CDATA[

Find the number of bytes per inode on Solaris
First do a df -k to get the device path:
df -k /local/iw-store
Mounted on /dev/vx/dsk/datadg/local
Then use mkfs -m to find frag size.
/usr/sbin/mkfs -m /dev/vx/dsk/datadg/local
mkfs -F ufs -o nsect=64,ntrack=32,bsize=8192,fragsize=1024,
cgsize=49,free=1,rps=120,nbpi=8186,opt=t,apc=0,gap=0,
nrpos=8,maxcontig=64,mtb=n /dev/vx/dsk/datadg/local 184320000

You can also use df -g &#124; grep ‘block size’
bash-2.03$ df -g &#124; grep ‘block size’
/    [...]]]></description>
		<wfw:commentRss>http://www.littleforest.co.uk/unix/how-to-find-the-number-of-bytes-per-inode-on-solaris/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

