CAcert System Admins discussion list

[Wytze van der Raay <wytze AT cacert.org>]

Op 11-1-2010 15:32, Ian G schreef:
> Switching across to sysadm list.  Story so far:  test1 got messed up
> because it ran out of space.

Managing growing logs and growing directories seems one of the
most vital points to keep CAcert's servers going :-)

> On 10/01/2010 15:51, Jan Dittberner wrote:
>>> /chroot/var/lib/php4:
>>>
>>> root@muley:/chroot/var/lib#
>>>  ls -la
>>> total 80916
>>> drwxr-xr-x 3 root root     4096 Jul 21  2006 .
>>> drwxr-xr-x 6 root root     4096 Aug 14  2008 ..
>>> drwxrwxrwx 2 root root 82763776 Jan  5 14:18 php4
>>
>> looks like a LOT of old session data. Something like tmpreaper or a
>> job which
>> uses find to cleanup old unused files from php's session store would
>> be a good idea.

The php4-common package contains a file /etc/cron.d/php4 with a cron
job to clean up the standard directory (/var/lib/php4). When running
php in a chroot'ed environment, that script can be edited to do the
same thing in the chroot environment. Here is what we have on the
production server:

 09,39 *     * * *     root   [ -d /home/cacert/var/lib/php4 ] && find
/home/cacert/var/lib/php4/ -type f -cmin +$(chroot /home/cacert
/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm

> ...
> Jan has a potential cron job.  PG suggests that any cron job to clean it
> out is a sysadm issue not a software issue.

I tend to agree with that.

> ...
> For critical team:  this is the sort of thing where test1 and other test
> machines should be aligned with the critical setup, and there should be
> some sort of doco we could follow from them?
> 
> Wytze, do we have any writings in place that talks about cron jobs and
> process start ups on reboots?

There is some documentation in place, please look at:
   http://wiki.cacert.org/SystemAdministration/Systems/Webdb
under Software Configuration ... Cron Jobs, but it is not complete yet.

Regards,
-- wytze

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature