1: <html>
2: <head>
3: <title>LON-CAPA CVS Upgrade</title>
4: </head>
5: <body>
6: <h1>LON-CAPA CVS Upgrade</h1>
7: <h3>Current CVS Upgrade Procedure</h3>
8: <p>
9: Scott Harrison
10: </p>
11: <p>
12: Last updated: 4/18/2001
13: </p>
14: <ul>
15: <li><a href="#fileupgrade">CVS Upgrade</a></li>
16: <li><a href="#rpm">RPM Upgrade</a></li>
17: <li><a href="#status">Viewing the status of your machine</a></li>
18: <li><a href="#setting">Setting yourself up for CVS</a></li>
19: </ul>
20: <a name="fileupgrade">
21: <h3>CVS Upgrade</h3>
22: <p>
23: If you have not yet set yourself up for LON-CAPA CVS, please see the
24: section <a href="#setting">"Setting yourself up for LON-CAPA CVS"</a>.
25: </p>
26: <p>
27: Before you do a file upgrade, you can always enter a "make statuspost"
28: command to see what will be changing on your system. See the section
29: <a href="#status">Viewing the status of your machine</a>.
30: </p>
31: <p>
32: If you have not yet set yourself up for LON-CAPA CVS, please see the
33: section <a href="#setting">"Setting yourself up for LON-CAPA CVS"</a>.
34: </p>
35: <p>
36: Assuming that you have set yourself up for LON-CAPA CVS, periodically
37: upgrading your system is a simple process.
38: </p>
39: <table border>
40: <tr><td><b>Steps</b></td><td><b>Commands</b></td></tr>
41: <tr><td>Make sure you are logged in for CVS</td>
42: <td>export CVSROOT=:pserver:USERNAME@zaphod.lite.msu.edu:/home/cvs
43: <br />cvs login</td></tr>
44: <tr><td>Go to your repository directory</td><td>cd loncapa</td></tr>
45: <tr><td>Update your CVS sources</td><td>cvs update -d</td></tr>
46: <tr><td>Go to the build directory</td><td>cd loncom/build</td></tr>
47: <tr><td>Become 'root'</td><td>su</td></tr>
48: <tr><td>Install/update static files</td><td>make install</td></tr>
49: <tr><td>Install/update dynamically configurable files<br />
50: <i>this preserves the current settings of your machine, don't worry :)</i>
51: </td>
52: <td>make configinstall</td></tr>
53: <tr><td>Restart your web server<br />Due to an apache bug, you should
54: enter this command twice. Restarting the web server will
55: <ul>
56: <li>introduce changes made to /home/httpd/lib/perl/Apache/*.pm files;</li>
57: <li>update user and group permissions if /etc/passwd or /etc/group change.</li>
58: </ul>
59: </td>
60: <td>/etc/rc.d/init.d/httpd restart
61: <br />/etc/rc.d/init.d/httpd restart</td></tr>
62: <tr><td>Restart the lonc/lond processes<br />Be patient (this takes several minutes).</td>
63: <td>/etc/rc.d/init.d/loncontrol restart</td></tr>
64: <tr><td colspan=2>After CVS logging in, you can always cut and paste this line
65: below assuming you do everything as root :)<br />
66: <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>
67: </table>
68: <p>
69: It may be also advisable to test your system after an upgrade if there are
70: critical tasks it is being used for.
71: </p>
72: <a name="rpm">
73: <h3>RPM Upgrade</h3>
74: <p>
75: There are three things involved in an RPM upgrade:
76: </p>
77: <ul>
78: <li>
79: <li>
80: <li>
81: </ul>
82: <a name="status">
83: <h3>Viewing the status of your machine</h3>
84: <p>
85: </p>
86: <a name="setting">
87: <h3>Setting yourself up for CVS</h3>
88: <p>
89: </p>
90:
91: </body>
92: </html>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>