From owner-freebsd-isp@FreeBSD.ORG Sun Aug 21 03:05:23 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B46D16A41F for ; Sun, 21 Aug 2005 03:05:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D59B43D45 for ; Sun, 21 Aug 2005 03:05:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j7L35LTT001383; Sat, 20 Aug 2005 22:05:21 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4307EF82.7080003@centtech.com> Date: Sat, 20 Aug 2005 22:05:38 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.10) Gecko/20050815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ovidiu Ene References: <430656A8.5030103@unixware.ro> In-Reply-To: <430656A8.5030103@unixware.ro> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1034/Thu Aug 18 15:07:58 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-isp@freebsd.org Subject: Re: Load Balancing - Nice and Easy - no BGP, no isp help. X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 03:05:23 -0000 Ovidiu Ene wrote: > Hello friends > > I am trying for a while to make a load balancer under FreeBSD. No BGP > support from isps! > > I would have: 3 nics, ISP1 nic, ISP2 nic and LAN nic. > What i've done until now, after reading lots of posts, googling for a > while: > > - I've suceeded to setup an outgoing load balancer with pf, it works > perfectly but only for outgoing traffic; > - I've noticed that almost everybody thing that it cannot be done load > balancing with BSD of incoming and outgoing without help of that both > ISP (BGP) > - I find hardware with proprietary OS/firmware that can do load > balancing without support of ISP. Some are cheap (300$), but at review > does not know to load balance incoming traffic (break functionality of > some pages accessed, since some of load is on one interface, some of > other, works corectly only if i setup to come some type of traffic on > one interface, some of other (for example trafic via port 80 on one nic, > ftp traffic on the other), also are expensive hardware load balancers > (over 1000$) that... i am asking myself how it works, without help of isp. > - I've found somewhere that it can be done load balancing but not with > one box with that 3 nics, but with 3 boxex, because (that article i am > "insipring" said that every box has just one routing table) because can > be created a virtual server that with handle routes from that 2 boxes. > - People told me that in Linux load balancing cand be done, 3 nics, 2 > external, one to Lan, with iptables. Here is a short article: > http://linux.com.lb/wiki/index.pl?node=Load%20Balancing%20Across%20Multiple%20Links > > > So, my question is, if some people made it (in expensive hardware that > did have the same OS, maybe even FreeBSD, and proprietary algorythms) > and in Linux it can be done (people told me, i've read articles and also > so it here, where i live) why it cannot be done under FreeBSD? > I guess it can be done, I want to do it with FreeBSD, and want to obtain > same performances as with Linux. > > What is your opinion about that? What should I do? Anybody suceed in > making load balancing work that way? I'm wondering if there is a way to do something like this with ipnat. If not, it might be a good place to toss something like this - just send new connection requests through alternating interfaces.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-isp@FreeBSD.ORG Sun Aug 21 05:59:51 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F167816A41F for ; Sun, 21 Aug 2005 05:59:51 +0000 (GMT) (envelope-from premal.mishra@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DD6C43D53 for ; Sun, 21 Aug 2005 05:59:51 +0000 (GMT) (envelope-from premal.mishra@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so747257wra for ; Sat, 20 Aug 2005 22:59:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Hm4VDECnZSufXmy7nogTIYaB7+mEs3elobXul0178GJJ5cYlOEVbp981k0GcEpQvqsbj3/GnPLAywydRA3dXg68rH8vtqT/LsNiPF1jMWZfkYgmKlMWwfN8DJpG4jYgUCCaL9oN+0sM9gif/4UCZS/LAwr6/q9XBeYDidXgGOVI= Received: by 10.54.142.2 with SMTP id p2mr3229465wrd; Sat, 20 Aug 2005 22:59:50 -0700 (PDT) Received: by 10.54.7.18 with HTTP; Sat, 20 Aug 2005 22:59:50 -0700 (PDT) Message-ID: <2211edca0508202259442a0610@mail.gmail.com> Date: Sat, 20 Aug 2005 22:59:50 -0700 From: Premal Mishra To: freebsd-isp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: ELF Binary Type '0' Not Known X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 05:59:52 -0000 Hi, Trying to run a binary file and it gives me an error :=20 "ELF Binary Type 0 Not Known" How can i fix this? Regards, Premal. From owner-freebsd-isp@FreeBSD.ORG Sun Aug 21 08:00:05 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0C5F16A41F for ; Sun, 21 Aug 2005 08:00:05 +0000 (GMT) (envelope-from khaled.abu@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC8743D45 for ; Sun, 21 Aug 2005 08:00:05 +0000 (GMT) (envelope-from khaled.abu@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so539413nzo for ; Sun, 21 Aug 2005 01:00:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GYOOFpNXVM4Iy9gIPey8lQy3VMOu+rI1yuRvkX/N49s6yVt0lREhutUogbwB4u1j1xOJsTme4Fz5ms/BnvuTudNyFiwNyDUeY32fvwNEMoNuJePJm17QXP7VGJ1dotKD/kd9l3JQ1WkawQObDhUwEpvUz2b3yphuQZ5IZtlABBI= Received: by 10.37.20.64 with SMTP id x64mr921nzi; Sun, 21 Aug 2005 01:00:04 -0700 (PDT) Received: by 10.36.251.14 with HTTP; Sun, 21 Aug 2005 01:00:04 -0700 (PDT) Message-ID: Date: Sun, 21 Aug 2005 11:00:04 +0300 From: Abu Khaled To: Premal Mishra In-Reply-To: <2211edca0508202259442a0610@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <2211edca0508202259442a0610@mail.gmail.com> Cc: freebsd-isp@freebsd.org Subject: Re: ELF Binary Type '0' Not Known X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 08:00:06 -0000 On 8/21/05, Premal Mishra wrote: > Hi, >=20 > Trying to run a binary file and it gives me an error : >=20 > "ELF Binary Type 0 Not Known" >=20 > How can i fix this? >=20 > Regards, > Premal. What type of binary do you have? # readelf -h look for OS/ABI it lists the binary type eg: OS/ABI: UNIX - Linux --=20 Regards. Abu Khaled From owner-freebsd-isp@FreeBSD.ORG Sun Aug 21 14:16:03 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7710F16A41F for ; Sun, 21 Aug 2005 14:16:03 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1738943D45 for ; Sun, 21 Aug 2005 14:16:01 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.12.11/8.13.1) with ESMTP id j7LEFuNB014271; Sun, 21 Aug 2005 10:15:56 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.12.11/8.13.1/Submit) id j7LEFuZ0014270; Sun, 21 Aug 2005 10:15:56 -0400 (EDT) (envelope-from bv) Date: Sun, 21 Aug 2005 10:15:51 -0400 From: Bill Vermillion To: Abu Khaled Message-ID: <20050821141551.GC13575@wjv.com> References: <2211edca0508202259442a0610@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.6i X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bilver.wjv.com Cc: freebsd-isp@freebsd.org Subject: Re: ELF Binary Type '0' Not Known X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 14:16:03 -0000 Even though on Sun, Aug 21, 2005 at 11:00 Abu Khaled realized that everything he says should be taken 'cum grano salis', he unhesitatingly continued with this missive: > On 8/21/05, Premal Mishra wrote: > > Hi, > > Trying to run a binary file and it gives me an error : > > "ELF Binary Type 0 Not Known" > > How can i fix this? > > Regards, > > Premal. > > What type of binary do you have? > # readelf -h > look for OS/ABI it lists the binary type > eg: OS/ABI: UNIX - Linux I've used 'brandelf' to fix problems like this in the past. I've had some Linux binaries that did not like 0 and branding them type 3 cured the problem. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-isp@FreeBSD.ORG Mon Aug 22 22:38:45 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C83F16A425 for ; Mon, 22 Aug 2005 22:38:45 +0000 (GMT) (envelope-from matt@frii.com) Received: from mail.frii.com (phobos01.frii.net [216.17.128.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 058B643D46 for ; Mon, 22 Aug 2005 22:38:44 +0000 (GMT) (envelope-from matt@frii.com) Received: from elara.frii.com (elara.frii.com [216.17.128.39]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.frii.com (FRII) with ESMTP id 5E8141DE9A0 for ; Mon, 22 Aug 2005 16:38:44 -0600 (MDT) Date: Mon, 22 Aug 2005 16:38:43 -0600 (MDT) From: Matt Ruzicka X-X-Sender: mattr@elara.frii.com To: freebsd-isp@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Creating a Log Retention Policy X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 22:38:45 -0000 Last year I attended a session at USENIX on system logging in which the instructor (Marcus Ranum) discussed the importance of having a clearly defined (and enforced) log retention policy. From what I remember of this portion of the lecture (the slides and my notes are lacking in details) he stressed that this policy would help significantly in the case of litigation, but it obviously would also give a solid policy for defining expectations and maintaining consistency between servers. A year later (*cough, cough*) I've started to compile ideas for this policy, but am having a bit of trouble finding good guidelines to follow. I was wondering if others currently had a clearly defined log retention policy for their organization and, if so, how they went about creating it? Thanks in advance for any feedback. Matthew Ruzicka - Systems Administrator Front Range Internet, Inc. matt@frii.net - (970) 212-0728 Got SPAM? Take back your email with MailArmory. http://www.MailArmory.com From owner-freebsd-isp@FreeBSD.ORG Mon Aug 22 23:31:41 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DB4B16A41F for ; Mon, 22 Aug 2005 23:31:41 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB9DF43D46 for ; Mon, 22 Aug 2005 23:31:40 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A5D89.dip.t-dialin.net [84.154.93.137]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j7MNVbxr087217; Tue, 23 Aug 2005 01:31:38 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j7MNVXXX023633; Tue, 23 Aug 2005 01:31:34 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j7MNW0g7012196; Tue, 23 Aug 2005 01:32:00 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200508222332.j7MNW0g7012196@fire.jhs.private> To: Matt Ruzicka In-Reply-To: Message from Matt Ruzicka of "Mon, 22 Aug 2005 16:38:43 MDT." Date: Tue, 23 Aug 2005 01:32:00 +0200 From: "Julian H. Stacey" Cc: freebsd-isp@freebsd.org Subject: Re: Creating a Log Retention Policy X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 23:31:41 -0000 Matt Ruzicka wrote: > Last year I attended a session at USENIX on system logging in which the > instructor (Marcus Ranum) discussed the importance of having a clearly > defined (and enforced) log retention policy. From what I remember of this > portion of the lecture (the slides and my notes are lacking in details) he > stressed that this policy would help significantly in the case of > litigation, but it obviously would also give a solid policy for defining > expectations and maintaining consistency between servers. > > A year later (*cough, cough*) I've started to compile ideas for this > policy, but am having a bit of trouble finding good guidelines to follow. > > I was wondering if others currently had a clearly defined log retention > policy for their organization and, if so, how they went about creating it? > > Thanks in advance for any feedback. > > Matthew Ruzicka - Systems Administrator This seems a general Sys Admin issue appropriate to SAGE http://www.sage.org , rather than anything needing to be BSD specific. The search box on their site with "archival policy" shows this at top: --- This represents the suggested policy document outline as it appears in A Guide to Developing Computing Policy Documents published by the USENIX Assocation for the SAGE. The guide is part of the SAGE series Short Topics in System Administration. -- Julian Stacey Consultant Systems Engineer, Munich. http://berklix.com Mail in Ascii (Html = Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-isp@FreeBSD.ORG Tue Aug 23 05:54:05 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0836816A41F for ; Tue, 23 Aug 2005 05:54:05 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DB6743D53 for ; Tue, 23 Aug 2005 05:54:04 +0000 (GMT) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id D915D8A006E; Mon, 22 Aug 2005 22:53:49 -0700 (PDT) Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 54622-03-15; Mon, 22 Aug 2005 22:53:45 -0700 (PDT) Received: from imap.sd73.bc.ca (smtp.sd73.bc.ca [10.10.10.15]) by smtp.sd73.bc.ca (Postfix) with ESMTP id D1B078A0024; Mon, 22 Aug 2005 22:53:29 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 7B15C18CC4C; Mon, 22 Aug 2005 22:53:28 -0700 (PDT) Received: from imap.sd73.bc.ca ([127.0.0.1]) by localhost (mailtest.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 98235-23; Mon, 22 Aug 2005 22:53:26 -0700 (PDT) Received: by imap.sd73.bc.ca (Postfix, from userid 80) id D261218CC3F; Mon, 22 Aug 2005 22:53:26 -0700 (PDT) Received: from 24.71.128.63 (SquirrelMail authenticated user fcash) by imap.sd73.bc.ca with HTTP; Mon, 22 Aug 2005 22:53:26 -0700 (PDT) Message-ID: <63196.24.71.128.63.1124776406.squirrel@imap.sd73.bc.ca> In-Reply-To: References: Date: Mon, 22 Aug 2005 22:53:26 -0700 (PDT) From: "Freddie Cash" To: "Matt Ruzicka" User-Agent: SquirrelMail/1.5.1 [CVS] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca X-Virus-Scanned: by amavisd-new using ClamAV at sd73.bc.ca Cc: freebsd-isp@freebsd.org Subject: Re: Creating a Log Retention Policy X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fcash@ocis.net List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 05:54:05 -0000 > Last year I attended a session at USENIX on system logging in which > the instructor (Marcus Ranum) discussed the importance of having a > clearly defined (and enforced) log retention policy. From what I > remember of this portion of the lecture (the slides and my notes are > lacking in details) he stressed that this policy would help > significantly in the case of litigation, but it obviously would also > give a solid policy for defining expectations and maintaining > consistency between servers. > A year later (*cough, cough*) I've started to compile ideas for this > policy, but am having a bit of trouble finding good guidelines to > follow. > I was wondering if others currently had a clearly defined log > retention policy for their organization and, if so, how they went > about creating it? We use newsyslog(8) to rotate the logs monthly, and store 13 backups, all neatly bzip'd. And we copy the backups to a pair of external USB drives where one is always off-site. Works great for our mail gateway, firewalls, and web servers. There's nothing officially written up anywhere, though. -- Freddie Cash, CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash@sd73.bc.ca helpdesk@sd73.bc.ca From owner-freebsd-isp@FreeBSD.ORG Tue Aug 23 06:14:05 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAB9B16A41F for ; Tue, 23 Aug 2005 06:14:05 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7252243D45 for ; Tue, 23 Aug 2005 06:14:05 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.90] (pool-71-109-145-221.lsanca.dsl-w.verizon.net [71.109.145.221]) (authenticated bits=0) by zoot.lafn.org (8.13.1/8.13.1) with ESMTP id j7N6E2RR032203 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Mon, 22 Aug 2005 23:14:04 -0700 (PDT) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <63196.24.71.128.63.1124776406.squirrel@imap.sd73.bc.ca> References: <63196.24.71.128.63.1124776406.squirrel@imap.sd73.bc.ca> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Mon, 22 Aug 2005 23:14:03 -0700 To: freebsd-isp@freebsd.org X-Mailer: Apple Mail (2.734) X-Virus-Scanned: ClamAV 0.86.2/1035/Mon Aug 22 04:37:18 2005 on zoot.lafn.org X-Virus-Status: Clean Subject: Re: Creating a Log Retention Policy X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 06:14:06 -0000 On Aug 22, 2005, at 22:53, Freddie Cash wrote: > Last year I attended a session at USENIX on system logging in which > the instructor (Marcus Ranum) discussed the importance of having a > clearly defined (and enforced) log retention policy. From what I > remember of this portion of the lecture (the slides and my notes are > lacking in details) he stressed that this policy would help > significantly in the case of litigation, but it obviously would also > give a solid policy for defining expectations and maintaining > consistency between servers. > > A year later (*cough, cough*) I've started to compile ideas for this > policy, but am having a bit of trouble finding good guidelines to > follow. > > I was wondering if others currently had a clearly defined log > retention policy for their organization and, if so, how they went > about creating it? I have one. The way I established it was to identify all the log files that might contain information of interest. Then for each I determined, based on previous usage, how long I needed to have them immediately available on-line. That determined the settings in newsyslog. We do backups to DVD (and off-site) weekly so some of the logs are retained a bit longer than necessary to be sure they get on at least 2 different DVDs. The determination of how long to retain the DVDs was more administrative than technical or usage based. We keep two full calendar years of old DVDs plus the current years. Anything older gets destroyed. Long term storage is on DVD. The current year is kept off-site. The 2 previous years are on-site. We keep 2 additional off-site copies of the current info (whatever is necessary to rebuild from a total site loss). Thats generally quite a bit more than the log files, but they are part of it. Once it was all defined, I just wrote it down. Its a small document that has only existed to be able to say we have it. No one ever reads it and there has never been a need to have it. But it could happen. From owner-freebsd-isp@FreeBSD.ORG Fri Aug 26 13:35:38 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97B4916A41F for ; Fri, 26 Aug 2005 13:35:38 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (r3ar5.chello.upc.cz [213.220.235.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E40843D48 for ; Fri, 26 Aug 2005 13:35:37 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id 7E98971B; Fri, 26 Aug 2005 15:35:35 +0200 (CEST) Message-ID: <430F1AAA.3040100@quip.cz> Date: Fri, 26 Aug 2005 15:35:38 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: ruben@bloemgarten.demon.nl References: <20050819184711.8A86C43D53@mx1.FreeBSD.org> In-Reply-To: <20050819184711.8A86C43D53@mx1.FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org Subject: Re: migration from mysql 3.2.23 to 4.1.13 X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Aug 2005 13:35:38 -0000 Don't forget to repair all tables /databases befor dump. I recommend you to convert ISAM tables to MyISAM before dump. (but do it on backup copy of data, not on original) Dump databases by newer mysqldump. If you are using non latin1 charset, maybe you will have some troubles after importing dump into 4.1. Do not blindly dump and reimport mysql users (table `user` from database `mysql`) because 4.1 has different structure and using different passwords. Manualy recreate all accounts instead. Ruben Bloemgarten wrote: > Hi Mario, > The dump was done on 3.23. I'll give 4.1 a try on that machine, sounds like > a nice hack though,using mysqldump 4.1 on a 3.23 database. Thanks for the > tip. > > Ruben > > -----Original Message----- > From: mario [mailto:mario@schmut.com] > Sent: August 19, 2005 8:37 PM > To: ruben@bloemgarten.demon.nl > Cc: james@jpri.com; freebsd-isp@freebsd.org > Subject: RE: migration from mysql 3.2.23 to 4.1.13 > > So, Ruben Bloemgarten wrote: > >>Hi James, >> >>That was the first thing I tried, unfortunately that does not work as >>the way 3.23 deals with ISAM is different to 4.1 and so it spits out >>errors when it runs into unrecognizable syntax. If you have managed to >>use mysqldump for a migration I would very much appreciate hearing about >>it as it would simplify things conisderably. > > > was this using mysldump 3.23 or 4.1? they produce different results and i > found one to work and the other not. i don't remember which did what but > just try the version you haven't yet. > > then there is also > http://dev.mysql.com/doc/mysql/en/upgrading-from-3-23.html > and then > http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html > > looking at the docs, it seems, you need to do a bit more than just a dump. > > hope this helps. i remember going from 4.0 to 4.1 was already fun. > > > mario;> > > > > >