New Message: Re: Towards zero-administration

[David A. Bayly]

>A new message was posted:
>
>Address: http://frontier.userland.com/discuss/msgReader$11716
>
>By: Samuel Reynolds (sam at spinwardstars.com)
>
>David Bayly's bayly.root (http://www.udena.ch/baylys/Bayly.root.sit) 
>includes a suite called "bounce" for automating some recommended 
>periodic operations for a Frontier server:
>
>* Save a copy and replace the original
>* restart Frontier (on a schedule and/or based on memory usage)
>
>Another thing that can bulk up your disk backups (and the likely 
>cause of your 300MB backups--I had >1GB before I tracked this down) 
>is Frontier's backup method for GDBs: back up all changed files in 
>the Guest Databases folder every night (settable via the Admin 
>site). This results in the creation of serially-numbered copies of 
>the changed .root files; each day when a GDB changes, a new copy is 
>created (and the old copies remain). I have a script that merges all 
>these GDB files into a single backup containing the most recent of 
>each GDB copy. Contact me at sam(at)SpinwardStars.com and I'll send 
>it to you. It hooks in nicely to mainResponder's nightlyBackup 
>callback.
>


Actually bayly.root has one of those too. It is called 
bayly.meregFrontierBackups.

Another issue is the logs that build up. I handle that by make a text 
extract and serving them on the web and discarding the log root;. I 
also mail out summaries of the log events that can be put down to a 
Manila website to the MEs of that site  That's  called 
bayly.gdblogTotext.

I schedule both of these scripts to run after the overnight tasks. .


-- 

- David Bayly.       Programmer and digest reader.     dbayly at udena dot ch
  		Digest Readers do it once a day.