did you observce cpu utilization and/or load average too?
yup. processes tends to slow down whenever the replication is at its peak.
in my case it looks like the cpu needs to: *take care of interrupts for 4 lan cards (heartbeat, drbd sync, backbone, and ltsp local net(x over lan))
why have a separate network for heartbeat? why not us a non-IP heartbeat (serial)? better yet, let heartbeat share your LTSP net so that failover will immediately take place whenever the cable is disconnected from network (although using IPFAIL is the proper way to do it). replication also slows down everytime an additional NIC is introduced on the machine.
*take care of all (4) X desktops and X apps (because of ltsp)
i'm more of an MSWin/Rdesktop fan than of LTSP/CygwinX. =) *CygwinX is the only X client for MSWin that i know that is free (but slow).
why not add OpenMosix to the server's & workstation's kernel so that processes will be distributed among them. read more about LTSP + OpenMosix.
HTH
-- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
