Sitat Hans Ekbrand <[EMAIL PROTECTED]>:
> > > > rsync from cron. > > But what if a user logs out, and in again before the cron job is > run? > If you have load balancing rather than fail-over then you risk that such a user ends up on the node that still has not been synced with the contents of the other. For a fail-over solution, the chances of someone logging out and then in again between syncs - and the passive node having taken over from the active - should be very small indeed. Anyway, rsync is smart enough to only update what's changed in individual files, so the problem is only transient. Unless you use shared storage it very difficult to totally guard against data loss/corruption. Depending on load and capacity of servers and interlinking (I'd say three NICs in such boxes - the additional for the syncing) you should be able to have a frequency of 3 - 5 minutes between syncs. Even with rsync running via ssh (and thus loading the machines heavily) you can move a lot of data in 3 minutes on a dedicated 100 Mb/s link. -- Mvh Ragnar Wisl�ff ------------------ life is a reach. then you gybe. ------------------------------------------------------- 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
