From owner-freebsd-chat@FreeBSD.ORG Fri Jan 14 23:29:40 2005 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC40116A4E0 for ; Fri, 14 Jan 2005 23:29:40 +0000 (GMT) Received: from smtp.datapro.co.za (smtp2.datapro.co.za [196.3.164.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE63743D1D for ; Fri, 14 Jan 2005 23:29:39 +0000 (GMT) (envelope-from ultraviolet@omina.co.za) Received: from omina.co.za (morn.omina.co.za [196.41.199.54]) by smtp.datapro.co.za (Postfix) with ESMTP id 9F84539D1A for ; Sat, 15 Jan 2005 01:22:33 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by omina.co.za (Postfix) with ESMTP id 04D8F182A37 for ; Sat, 15 Jan 2005 01:29:35 +0200 (SAST) Received: from omina.co.za ([127.0.0.1]) by localhost (omina.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71245-01 for ; Fri, 14 Jan 2005 23:29:28 +0000 (GMT) Received: by omina.co.za (Postfix, from userid 1001) id EC28618298A; Sat, 15 Jan 2005 01:29:27 +0200 (SAST) Date: Sat, 15 Jan 2005 01:29:27 +0200 From: William Fletcher To: freebsd-chat@freebsd.org Message-ID: <20050114232927.GR32999@omina.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at omina.co.za Subject: The useless human memory system... X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ultraviolet@turandot.net List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 23:29:41 -0000 Hi, During my teenage years I probably destroyed a few million brain cells from alcohol abuse and now I was wondering if anyone had a nice checklisting system to help me remember what I do on the few servers I'm incharge of... At the moment I use a normal file on every server which I modify with vi. It all sits in the file with sections and looks something like this... + Comment. % Command. - Normal config file. (Backup). ^ File/Directory to be backed up. ` Heavy backup, like mailboxes, websites, etc. * Option to be compiled into a port. = File already exists and is backed up, but a modification is required for this section. < Dependency package\port required to install package. # Section. ! End of section. @ Package\Port\Software installed. _ Yafic file integrity rule. $ Things to ask ISP\Customer\Co-worker. And I use it like... # Manually installed software. @ postfixadmin. = /etc/fstab % chroot /usr/local/jails/webserver /usr/local/sbin/htpasswd -c /usr/local/www/mailadmin.server.co.za/admin/.htpasswd admin % mkdir -p /usr/local/jails/webserver/usr/local/virtual % chown 5000:5000 /usr/local/jails/webserver/usr/local/virtual = /usr/local/jails/webserver/usr/local/etc/apache2/httpd.conf - /usr/local/www/mailadmin.server.co.za/config.inc.php - /usr/local/www/mailadmin.server.co.za/delete.php - /usr/local/www/mailadmin.server.co.za/admin/delete.php - /usr/local/jails/webserver/root/bin/mbdelete.sh = /usr/local/jails/webserver/usr/local/etc/sudoers ! Then, I can use sed\grep and create a script of all files modified, I can use this to create tar archives for each server incase something should go so wrong and I cannot `restore` off a tape. I also know exactly what I did on what server, what to add so as not to disturb file integrity, and so forth. I was just wondering if I'm crazy or if there is an even better method of keeping track of what is going on, keeping all the little gears oiled and running smoothly on my servers... -- William Alexander Fletcher It has yet to be proven that intelligence has any survival value. -- Arthur C. Clarke