I didn't see this mentioned in the archives, so I thought I'd share it.

In the process of building a LTSP-based renderfarm for a customer, I had
to compile my own kernel from the RH 7.3 sources (for reasons that I
won't get into).  As you may or may not now, RedHat has a bunch of their
own patches to the 2.4.18 kernel, so the Swap-over-NFS NFS patch does
not apply cleanly.  In order to avoid porting the patch to the work with
the RedHat kernel, and to avoid using any third-party patches at all, I
started looking for another way to Swap-over-NFS.  Here is what I've
done:

- Compile the kernel for the workstations to include support for loop
devices (CONFIG_BLK_DEV_LOOP=[y|m])
- Copy your server's /sbin/losetup to /opt/ltsp/i386/sbin
- In /opt/ltsp/i386/etc/rc.local, change:
        swapon ${SWAPFILE}
  to:
        /sbin/losetup /dev/loop0 ${SWAPFILE}
        swapon /dev/loop0

The performance of swapping via the loop device might be slower than
using the kernel patch (I haven't done any comparisons), but since I'm
only doing this as a last-resort fallback for my render nodes (each has
2GB RAM), I'm not really worried about it).

After making this change, and using tmpfs instead of a ramdisk for /tmp
(my render nodes need more than a few MB of temp space), I couldn't be
happier with LTSP.

Thanks for the great work!

Now if I could only figure out how to get dhclient to exit gracefully so
/oldmount gets unmounted...

-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to