* Present: Aybars, Dan, Kevan, Skylar
* Talked about wire management in D224 closet
- D-rings on mounting board
- Two 3ft racks to split heat/cables
- In-rack cable management
- Mountings for all equipment
- Panduit for fiber
- Cut vents in doors?
* Two CS VLANs:
- One for public ports in Dennis, connected off most ports on Summit 48. No NFS/NIS; only XDM/SSH to private VLAN. DHCP forwarded to private VLAN.
- One for private traffic (e.g. servers). Entire Summit 24 can be dedicated to this, with a few ports on the Summit 48 for the admin office, Charlie's office, and 4th floor closet.
* Figure out what's up with quarkprime
* Configure PHP-GD for Toby
Present: Dan, CharlieP, Skylar
* quarkprime login (Skylar, Dan)
* TomS (CharlieP)
* nmh (Skylar)
* Talk to Kevan about next Wednesday meeting (Skylar)
Present: CharlieP, Aybars, Dan, Skylar
* Quark' (Dan, Aybars)
* Colored backing on ACL sign (Skylar)
* Get chair list from Mary Lou (Skylar)
* Log host on bagend (Skylar)
* Get admin cluster functional (Skylar, Aybars)
* Test FTP from Miller Farm (CharlieP)
I'm stil battling the problem with Apache. I've been paring down our installation to the bare essentials to try to isolate what the problem component is. I've turned off all unnecessary PHP extensions, unloaded all unused Apache modules, and completely uninstlled mod_auth_pgsql because it no longer supports FreeBSD.
While looking through the port manifest for Postgres 8.0 on quarkprime, I noticed that the FreeBSD package contains scripts that automate daily vacuuming and backups of the database. I've upgraded quark from 7.4.7 to 8.0.1. I had to do a pg_dumpall and then a restore to do the upgrade because of the major version change.
These are enabled by adding these two lines to /etc/periodic.conf:
daily_pgsql_backup_enable="YES"
daily_pgsql_vacuum_enable="YES"
The backups are done on individual databases using pg_dump, and are plopped in /usr/local/pgsql/backups. Because periodic stuff is run at 3AM, I've moved the amanda invocation from 3AM to 4AM.