doc/build/cvsupgrade.html - view

File: [LON-CAPA] / doc / build / Attic / cvsupgrade.html
Revision 1.1: download - view: text, annotated - select for diffs
Wed Apr 18 15:55:38 2001 UTC (23 years, 6 months ago) by harris41
Branches: MAIN
CVS tags: HEAD

adding in information about CVS upgrade -Scott

<html> <head> <title>LON-CAPA CVS Upgrade</title> </head> <body> <h1>LON-CAPA CVS Upgrade</h1> <h3>Current CVS Upgrade Procedure</h3> <p> Scott Harrison </p> <p> Last updated: 4/18/2001 </p> <ul> <li><a href="#fileupgrade">CVS Upgrade</a></li> <li><a href="#rpm">RPM Upgrade</a></li> <li><a href="#status">Viewing the status of your machine</a></li> <li><a href="#setting">Setting yourself up for CVS</a></li> </ul> <a name="fileupgrade"> <h3>CVS Upgrade</h3> <p> If you have not yet set yourself up for LON-CAPA CVS, please see the section <a href="#setting">"Setting yourself up for LON-CAPA CVS"</a>. </p> <p> Before you do a file upgrade, you can always enter a "make statuspost" command to see what will be changing on your system. See the section <a href="#status">Viewing the status of your machine</a>. </p> <p> If you have not yet set yourself up for LON-CAPA CVS, please see the section <a href="#setting">"Setting yourself up for LON-CAPA CVS"</a>. </p> <p> Assuming that you have set yourself up for LON-CAPA CVS, periodically upgrading your system is a simple process. </p> <table border> <tr><td><b>Steps</b></td><td><b>Commands</b></td></tr> <tr><td>Make sure you are logged in for CVS</td> <td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs <br />cvs login</td></tr> <tr><td>Go to your repository directory</td><td>cd loncapa</td></tr> <tr><td>Update your CVS sources</td><td>cvs update -d</td></tr> <tr><td>Go to the build directory</td><td>cd loncom/build</td></tr> <tr><td>Become 'root'</td><td>su</td></tr> <tr><td>Install/update static files</td><td>make install</td></tr> <tr><td>Install/update dynamically configurable files<br /> <i>this preserves the current settings of your machine, don't worry :)</i> </td> <td>make configinstall</td></tr> <tr><td>Restart your web server<br />Due to an apache bug, you should enter this command twice. Restarting the web server will <ul> <li>introduce changes made to /home/httpd/lib/perl/Apache/*.pm files;</li> <li>update user and group permissions if /etc/passwd or /etc/group change.</li> </ul> </td> <td>/etc/rc.d/init.d/httpd restart <br />/etc/rc.d/init.d/httpd restart</td></tr> <tr><td>Restart the lonc/lond processes<br />Be patient (this takes several minutes).</td> <td>/etc/rc.d/init.d/loncontrol restart</td></tr> <tr><td colspan=2>After CVS logging in, you can always cut and paste this line below assuming you do everything as root :)<br /> <tt>cd loncapa; cvs update -d; cd loncom/build; make install; make configinstall; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/httpd restart; /etc/rc.d/init.d/loncontrol restart</tt></td></tr> </table> <p> It may be also advisable to test your system after an upgrade if there are critical tasks it is being used for. </p> <a name="rpm"> <h3>RPM Upgrade</h3> <p> There are three things involved in an RPM upgrade: </p> <ul> <li> <li> <li> </ul> <a name="status"> <h3>Viewing the status of your machine</h3> <p> </p> <a name="setting"> <h3>Setting yourself up for CVS</h3> <p> </p> </body> </html>