I'm trying to run bzflag over a network, feeding a netstation. There's
not enough memory to run it natively, and running it on as a client
to the netstation operating as as an X server is _slow_, even with
differential compression running (dxcp). I suspect in this mode it is
saturating the ethernet.
So, providing just a little extra memory might fix things. bzflag is
very resource intensive, (one of the few apps which prompts swapping to
disk on my host machine), and I'm sure it is not all used all the
time; so I've reason to suspect this.
Trying to enable swap over nfs results in a rejection to the C swapon
function, even though swapon in principle could connect straight to
a file - clearly it rejects remote drives.
Yes, I know this makes the system critically prone to failure, if
something "important" is sent to swap which is remote over the network -
but as we access a complete filesystem on the host computer for general
operation, it does not make much difference, really.
Any ideas on how to get a bit of swap space over nfs (or, in broader
terms, a network) ?
Thanks,
--
John August
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
