Rolf-Werner Eilert wrote:
> [...]
> This is really a very good idea, but I see one more problem. From time 
> to time you will want to update software on the server. If you update 
> the software, some apps might write their data in another, new way and 
> users logging in to the other server after having worked with the 
> updated one might not be able to access their data anymore. Or even 
> worse, a new way of writing an .rc file might be corrupted if you start 
> the older version.
>
> How do you keep the two servers really up-to-date with EVERYTHING like 
> new apps and stuff?
>
> [...]
>
> Thanks for your comments.
>
> Rolf

Well, Chris Fanning has already given a good solution via Xen, but we 
used two different methods. At first times, we used to have two cheap 
servers with identical installations. Everytime we made an update on one 
server we did it in the other one too. It's very easy, but it isn't fast 
nor error-free.

Actual solution in our case at EjerciciosResueltos use Subversion. 
Everything but the homes are under version control. Of course, that does 
NOT mean that every file is under version control, since files in, say, 
/usr/bin are controlled by the distro's package control system, and 
files in, say, /var/log must be machine-specific to allow us to get 
usage info, problems detectionand such. But it IS important to use svn 
to keep control of the installed packages. We used a nightly cron task 
to update the machine from the repository, and to update every 
configuration from SVN.

Noel Torres
er Envite

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_____________________________________________________________________
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

Reply via email to