Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!hpfcso!hpfcmgw!dale
From: dale@hpfcmgw.HP.COM (Dale McCluskey)
Newsgroups: comp.sys.hp
Subject: Re: swap space for diskless clients
Message-ID: <1080149@hpfcmgw.HP.COM>
Date: 7 May 90 17:27:26 GMT
References: <1990Apr30.024120.20924@comp.vuw.ac.nz>
Organization: HP Fort Collins, CO
Lines: 27

Andrew Cunningham (ac1@rosemary.cs.reading.ac.uk) writes:
...
> The total swap on the server is divided amongst the cnodes in a shared
> cluster; no c-node has a limit short of the total; thus all the space
> is available for any given cnode.  

This is true unless "maxswapchunks" has been set for a particular client.
This is a kernel parameter that is documented in an appendix to the 
System Administration manual.  The parameter is enforced on the client, 
which allows for different clients to have different limits.

> [Unless you have local swap; then each node can swap to its local
> disk, and to a remote disk as well, i think, which makes things much 
> more complex for your purposes...]

If a client has local swap, that's all it can swap to; it can't use both
the local disk and the server's swap space.

I'll echo what others have said: "monitor" is the tool of choice for 
looking into this stuff - the "K" screen will be particularly helpful 
in this case.

							Dale


The above comments are from me, not HP.  They should *not* be taken as
an official statement by HP.