<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title>Worklog</title>
<link>http://www.earlham.edu/~littejo/worklog/</link>
<description>Work, notes, and projects.</description>
<copyright>Copyright 2006</copyright>
<lastBuildDate>March 29, 2006 03:55 PM</lastBuildDate>
<generator>http://www.movabletype.org/?v=2.63</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>General update</title>
<description><![CDATA[<p>Several projects eating time in the last couple of weeks.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006247.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006247.html</guid>
<category>Installations</category>
<pubDate>March 29, 2006 03:55 PM</pubDate>
</item>
<item>
<title>Solaris patches</title>
<description><![CDATA[<p>I&#8217;m getting bitten by Solaris patches.  In particular, several recent patches have decided to muck with /etc/rc3.d scripts in the postpatch script.  I remove a number of these scripts at Jumpstart time so that the systems they start won&#8217;t be started (things like automounter and volume management, which mostly serve to bite one in the hindquarters).  Sun adding them back in messes with my systems.  They have every right to modify the main file in /etc/init.d, but they should keep their hands off of my territory in /etc/rc?.d.</p>

<p>So I copied out the portion of my Jumpstart script that disables these, and I&#8217;ve made it a standalone script that can be run after any patches are applied.  Just run it.  Good maintenance, and swat those pesky Sun idjits.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006149.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006149.html</guid>
<category>Firefighting</category>
<pubDate>March 14, 2006 03:51 PM</pubDate>
</item>
<item>
<title>PacketShaper tuning</title>
<description><![CDATA[<p>I tweaked the PacketShaper a little this afternoon, after numerous comments that incoming connections were taking a long time (particularly e-mail related ones, like <span class="caps">IMAP, </span>and from multiple people).  I think the single biggest thing I did was to bump up the priority on the Default class for the main college address space from priority 1 to priority 3 (higher is better).  I seem to recall an offhand comment on the list at some point that the first few packets of a flow are usually unclassified and thus put into Default.  Increasing the priority of that lets them through faster and then lets them get classified faster, allowing them to take advantage of the policies and partitions for their particular traffic type that much sooner.  <span class="caps">IMAP </span>feels a lot faster, both in Pine and Mail.app now.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006119.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006119.html</guid>
<category>Other</category>
<pubDate>March 10, 2006 03:59 PM</pubDate>
</item>
<item>
<title>A lot of Cyrus work</title>
<description><![CDATA[<p>This week has been mostly a continuation of Cyrus <span class="caps">IMAP </span>work.  The system itself is ready for production use, but there are a number of helper scripts and utilities that need to be developed before we can start the migration.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006118.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006118.html</guid>
<category>Installations</category>
<pubDate>March 10, 2006 03:52 PM</pubDate>
</item>
<item>
<title>Pine and Perdition</title>
<description><![CDATA[<p>Testing Pine with Perdition &#8212; I have my .pinerc stored on the <span class="caps">IMAP </span>server, and I simply replaced all the hostnames that point to KE (mailer.earlham.edu) with ones that point to mailproxy.earlham.edu (Perdition and Sendmail running on <span class="caps">SIPALA</span>).</p>

<p>It works flawlessly.  I get my mail folders on <span class="caps">KE, </span>and I send mail through <span class="caps">SIPALA.</span></p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006059.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006059.html</guid>
<category>Installations</category>
<pubDate>March  2, 2006 06:56 PM</pubDate>
</item>
<item>
<title>SIPALA Notes</title>
<description><![CDATA[<p>Most of work this week has been working on <span class="caps">SIPALA </span>and various pieces of the new mail system.  At this point, just about everything is working.  I think the main things to do are VxFS/VxVM installation for the message store and considering a milter for antivirus checking.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/006058.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/006058.html</guid>
<category>Installations</category>
<pubDate>March  2, 2006 06:34 PM</pubDate>
</item>
<item>
<title>Cyrus, Perdition, LDAP</title>
<description><![CDATA[<p>I got Cyrus working again on Solaris, as per entries last spring.  Not terribly difficult.  The harder part was getting Perdition, the <span class="caps">IMAP</span>/POP3 proxy, working.  There are some source code errors that made the build on Solaris tricky.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005976.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005976.html</guid>
<category>Installations</category>
<pubDate>February 24, 2006 01:47 PM</pubDate>
</item>
<item>
<title>SULA, Big RAM</title>
<description><![CDATA[<p>Got <span class="caps">SULA </span>installed, mostly, and Aaron&#8217;s taking it over now.  It&#8217;s got 8GB of <span class="caps">RAM, </span>which entailed turning on the <span class="caps">PAE </span>extensions for FreeBSD&#8217;s kernel.  And that entailed making a static kernel, which entailed compiling in the <span class="caps">IPF</span>ilter stuff.  All is well now, and MySQL is up and running for development work.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005915.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005915.html</guid>
<category>Installations</category>
<pubDate>February 16, 2006 01:50 PM</pubDate>
</item>
<item>
<title>Lumana and Jumpstart tweaks</title>
<description><![CDATA[<p>There were still a few bugs in the <span class="caps">SVM </span>script that I was tweaking the other day, but I got them worked out, jumpstarted Lumana, and things are pretty good now.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005880.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005880.html</guid>
<category>Installations</category>
<pubDate>February 10, 2006 12:16 PM</pubDate>
</item>
<item>
<title>Jumpstart and V440</title>
<description><![CDATA[<p>The Solaris 9 version we had on <span class="caps">ROJ </span>was too ancient to support the new <span class="caps">V440, </span>so when it tried to boot in Jumpstart, it failed.  Updating the Solaris version in the Jumpstart area has always been a pain; something about the script seemed to always bomb out on <span class="caps">ROJ, </span>requiring editing of the script and running it from somewhere other than the <span class="caps">CD. </span> Fortunately,  Doug Hughes clued me in to the fact that all I had to do was copy the Solaris_9 directory contents from the <span class="caps">DVD </span>into the expected place in the Jumpstart area, and all would be good.</p>

<p>Next up, though, is making my volume manager Jumpstart script work with four disks.  It&#8217;s always assumed two disks for a simple mirroring setup, but the <span class="caps">V440 </span>has four, and I&#8217;d like to add those in to the mix at Jumpstart time, too.  I think I got it working now &#8212; now that I&#8217;ve removed a couple of lines of stale code that were causing a test bug and leaving the system in a pretty sad state.  To test it all tomorrow.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005867.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005867.html</guid>
<category>Installations</category>
<pubDate>February  8, 2006 05:07 PM</pubDate>
</item>
<item>
<title>SANs and LUNs and devices, oh my...</title>
<description><![CDATA[<p>Once you tell the <span class="caps">ITMPT </span>driver in Solaris that it can access more than the first <span class="caps">LUN </span>on a fibre channel device, mapping out the <span class="caps">SAN </span>makes a lot more sense.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005800.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005800.html</guid>
<category>Installations</category>
<pubDate>February  3, 2006 01:38 PM</pubDate>
</item>
<item>
<title>Wildcard SSL certificate</title>
<description><![CDATA[<p>We purchased an wildcard <span class="caps">SSL </span>certificate last week for use across our <span class="caps">SSL </span>services.  Installation has been pretty painless.  Apache is easy, sendmail and UW-IMAP are pretty straightforward.  The main holdouts are EZproxy and the <span class="caps">LDAP </span>servers.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005801.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005801.html</guid>
<category>Installations</category>
<pubDate>January 31, 2006 04:02 PM</pubDate>
</item>
<item>
<title>Server installs, continued...</title>
<description><![CDATA[<p>All the new servers, etc. have arrived and are in the racks.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005631.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005631.html</guid>
<category>Installations</category>
<pubDate>January 18, 2006 03:40 PM</pubDate>
</item>
<item>
<title>Toys!</title>
<description><![CDATA[<p>Santa brought me several cartloads of toys this year.  Still trying to get all of them unboxed, racked, and inspected, much less set up and configured.  That&#8217;s for the rest of winter.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005505.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005505.html</guid>
<category>Installations</category>
<pubDate>January  4, 2006 05:00 PM</pubDate>
</item>
<item>
<title>Moodle Upgrade</title>
<description><![CDATA[<p>I just grabbed the latest 1.5.3+ source code for <a href="http://moodle.org/">Moodle</a>, set the site in maintenance mode, untarred it, upgraded everything through the web admin interface, and turned off maintenance mode.  All looks good so far.</p>]]></description>
<link>http://www.earlham.edu/~littejo/worklog/archives/005486.html</link>
<guid>http://www.earlham.edu/~littejo/worklog/archives/005486.html</guid>
<category>Upgrades</category>
<pubDate>December 14, 2005 11:07 AM</pubDate>
</item>


</channel>
</rss>