The Apache log files tend to fill up disk space.
We clean these up every month or so by moving them
to a different partition.  The other partition is 
not backed up.  We are saving these so we can
do security and usage analyses.
<p>
Here's what to do next time this happens:
<ol>
<li> log on to the machine with the full disk, which is likely to be <code>andrews</code>, become root
<li> do
<pre>
   cd /usr
   du -dk . >& du.out
</pre>
<li>Come back awhile later, do
<pre>
   sort -nr du.out | head -40
</pre>

<li> Probably <code>local/apache-<i>N.M</i>/logs/200<i>Y</i>/<i>MM</i></code> is taking up lots of space.
   So, we move it:
<pre>
    cd /usr/local/apache/logs/2007
    mv 10 /export/home1/root/apache/logs/2007
    ln -s /export/home1/root/apache/logs/2007/10 .
</pre>
</ol>
More actions to take to clean up /export/home1 on andrews:
<ol>
<li>Compress the agent logs.  Apparently when the apache logs are moved for the previous month, the last few days of agent log files are not compressed, so we compress them:
<pre>
     <i>/usr/bin/find /export/home1/root/apache logs/</i>`date +%Y` -mtime +2 -name agent_log -size +1000000c -print > /tmp/agent_logs 
     /usr/local/adm/compress_agent_log `cat /tmp/agent_logs`
</pre>
<li>Gzip the apache logs:
<pre>
     cd /export/home1/root/apache/logs/2010
     gzip -9 */*/*log* 
</pre>
<li>
Stop the web server and rotate /export/home/tmp/php.err:
<pre>
     /etc/init.d/gsrc stop
     mv /export/home1/tmp/php.err /export/home1/tmp/php.err.4
     /etc/init.d/gsrc start
</pre>
</ol>