I have a 4-server setup that syncs users' /homes at point of login (called from an Xsession.d file), as well as on a nightly cron. It uses rsync connecting over Openswan VPNs, and works beautifully.
Not sure if I can attach files to list emails, so ping me if you'd like a copy of my scripts. -Michael On Tue, Mar 29, 2011 at 9:35 AM, Joseph Bishay <[email protected]> wrote: > > Hello, > > Thank you for telling us about your experiences! > > On Tue, Mar 29, 2011 at 4:38 AM, Chris Roberts <[email protected]> > wrote: > > We started out using Unison using /srv/shared on each LTSP server. This > > proved to be a bad idea, as Unison uses a lot of resources during the > > synchronisation process. It did a good job though of keeping the files in > > sync though. If you opted to use Unison then I would recommend separating > > the data and unison process from the LTSP server, so that the load does not > > impact on your users. Keeping data off the LTSP server is probably good > > practice anyway. > > So you're recommending having a separate server for /home? > > I know you can set up rsync to work both ways -- you just need to > specify how it acts when it comes across a newer file on the server, > and make sure that the two servers have identical clocks. > > > That said, whilst your case sounds more difficult - sharing home folders - > > in practice it is probably easier, as you should never have both copies > > being edited at the same time. Perhaps an rsync prompted by the user's > > logout? > > That may be a great idea -- have rsync/Unison triggered by the user logging > out. > > > But it mostly comes down to bandwidth - if you have decent synchronous > > bandwidth between the sites, then you have options. > > I don't have any special bandwidth between the buildings -- it would > have to go from one building -> through our ISP to the Internet then > down via the ISP at the second location to the server. I am imaging > that we'd hit our bandwidth cap very quickly. > > Joseph > > ------------------------------------------------------------------------------ > Enable your software for Intel(R) Active Management Technology to meet the > growing manageability and security demands of your customers. Businesses > are taking advantage of Intel(R) vPro (TM) technology - will your software > be a part of the solution? Download the Intel(R) Manageability Checker > today! http://p.sf.net/sfu/intel-dev2devmar > _____________________________________________________________________ > 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.freenode.net -- Michael Blinn People Places, Inc. www.peopleplaces.org --- CONFIDENTIALITY NOTICE: This message, and any attachments that may accompany it, contain information that is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, or otherwise exempt from disclosure under applicable law. If the recipient of this message is not the intended recipient, any disclosure, copying, or other use of this communication or any of the information, which it contains is unauthorized and prohibited. If you have received this message in error, please notify the original sender by return mail and delete this message, along with any attachments, from your computer. Thank you. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _____________________________________________________________________ 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.freenode.net
