From owner-ctm-users@FreeBSD.ORG Tue Jan 8 23:48:25 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 73B459E0 for ; Tue, 8 Jan 2013 23:48:25 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 3DD033CB for ; Tue, 8 Jan 2013 23:48:24 +0000 (UTC) Received: from [127.0.0.1] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.6/8.14.6) with ESMTP id r08NmN8p063309 for ; Tue, 8 Jan 2013 17:48:24 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <50ECB047.4030503@missouri.edu> Date: Tue, 08 Jan 2013 17:48:23 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: ctm-users@freebsd.org Subject: Re: More request for feedback. References: <50E12E1B.6090403@missouri.edu> <50E1D0C1.3020601@missouri.edu> In-Reply-To: <50E1D0C1.3020601@missouri.edu> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2013 23:48:25 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Based on responses so far, I am assuming that no-one is using ctm-cvs-cur any more. So I feel safe about deleting this in late February. Is anyone still using ctm-src-4 or ctm-src-5? Note that src-5 hasn't changed for three years, and src-4 for even longer. (The updates on 9/23/2012 were just header changes due to switching from cvs to svn.) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ7LBHAAoJEC3xK9GaktgHVbEH/AmXVWwtJiS9C33eabYy1jVH zQ/vqgVw8Pn1kHYUt2NtdU/ggLKxTAPRLxgiR3v/4Xg6NeoAI0PEwIDY4OnKTjeI roFWcvnklWOg/To5nCQ87IsizkiYWRPahGTj4pfJt9GMjSqGK7BjQ3I4frkwtuJ/ J0vonczwzGQaqEguq41cTlPU3RX0cEQJZD5hbfYr/78aHB02REwXXvij+fBDaiLH 3rzPwlXy6/brCNwkljUFAb6g1mmVIt0lFP34jZnPn8To+a6eUk3KXugGIlJLFDJL +Jb46+96T3MUYs3R66YLnCHoq1j1MczEMNMAkJZYBf5FaNL99b81cw6Fzd1fYBI= =Xzm3 -----END PGP SIGNATURE----- From owner-ctm-users@FreeBSD.ORG Thu Jan 10 23:33:49 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CF3BAD4C for ; Thu, 10 Jan 2013 23:33:49 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 7D146FE4 for ; Thu, 10 Jan 2013 23:33:49 +0000 (UTC) Received: from [127.0.0.1] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.6/8.14.6) with ESMTP id r0ANXYm0022680; Thu, 10 Jan 2013 17:33:34 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <50EF4FCE.1060405@missouri.edu> Date: Thu, 10 Jan 2013 17:33:34 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Julian H. Stacey" Subject: Re: More request for feedback. References: <201301102254.r0AMsPaQ094085@fire.js.berklix.net> In-Reply-To: <201301102254.r0AMsPaQ094085@fire.js.berklix.net> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ctm-users@freebsd.org X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2013 23:33:49 -0000 On 01/10/2013 04:54 PM, Julian H. Stacey wrote: > Stephen M wrote > >> Based on responses so far, I am assuming that no-one is using >> ctm-cvs-cur any more. So I feel safe about deleting this in late >> February. > > Fine. > ( I was keeping quite, still using CVS & thus ctm-cvs-cur, cos I hadn't got > round to trying svn from local repository for replacements for eg > cvs -R export -r RELENG_9_1_0_RELEASE src > cvs -R export -r RELEASE_9_1_0 ports > cvs -R export -r RELEASE_9_1_0 doc > (maybe others were similarly lurking ?) Syntax examples would be welcome. Actually this is the first time I have seen the "export" command for cvs! Anyway, this is what I would do. Suppose my repository is at /usr/home/stephen/svn. Then the first time I would run the commands cd where-I-want-to-put-it svn co file:///usr/home/stephen/svn/base/release/9.1.0 src svn co file:///usr/home/stephen/svn/ports/branches/RELENG_9_1_0 ports svn co file:///usr/home/stephen/svn/doc/release/9.1.0 doc I suspect that you could use export in place of co (checkout). Look at http://svn.freebsd.org/ to see what are the allowables after base, ports or doc. If you used checkout, then you could update it late with cd where-I-want-to-put-it svn up src ports doc where up is short for update. > > >> Is anyone still using ctm-src-4 or ctm-src-5? > > I'm still subscribed & scripts in place to update trees on every ctm stream, > but though I dont have any FreeBSD-5 boxes. I do have >= 3 boxes with FreeBSD-4 > that won't easily upgrade but yes: > >> Note that src-5 hasn't changed for three years, and src-4 for even >> longer. (The updates on 9/23/2012 were just header changes due to >> switching from cvs to svn.) > > Tracking 4 & 5 is a moot procedure, > it might as well stop if consuming needed resources. By far the majority of the resources go to ctm-cvs-cur. The resources for src-4 and src-5 are really quite small. So just for you, I'll keep it going. If you ever no longer need src-4 or src-5 email me on this mailing list (so that if anyone else still wants it I will keep it going). From owner-ctm-users@FreeBSD.ORG Thu Jan 10 23:42:34 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4FB54521 for ; Thu, 10 Jan 2013 23:42:34 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id B792CEA for ; Thu, 10 Jan 2013 23:42:33 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBF141.dip.t-dialin.net [217.251.241.65]) (authenticated bits=128) by flat.berklix.org (8.14.5/8.14.5) with ESMTP id r0AMs1It002886; Thu, 10 Jan 2013 23:54:02 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r0AMsblj047785; Thu, 10 Jan 2013 23:54:37 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r0AMsPaQ094085; Thu, 10 Jan 2013 23:54:31 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201301102254.r0AMsPaQ094085@fire.js.berklix.net> To: Stephen Montgomery-Smith Subject: Re: More request for feedback. From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Jan 2013 17:48:23 CST." <50ECB047.4030503@missouri.edu> Date: Thu, 10 Jan 2013 23:54:25 +0100 Sender: jhs@berklix.com Cc: ctm-users@freebsd.org X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2013 23:42:34 -0000 Stephen M wrote > Based on responses so far, I am assuming that no-one is using > ctm-cvs-cur any more. So I feel safe about deleting this in late > February. Fine. ( I was keeping quite, still using CVS & thus ctm-cvs-cur, cos I hadn't got round to trying svn from local repository for replacements for eg cvs -R export -r RELENG_9_1_0_RELEASE src cvs -R export -r RELEASE_9_1_0 ports cvs -R export -r RELEASE_9_1_0 doc (maybe others were similarly lurking ?) Syntax examples would be welcome. > Is anyone still using ctm-src-4 or ctm-src-5? I'm still subscribed & scripts in place to update trees on every ctm stream, but though I dont have any FreeBSD-5 boxes. I do have >= 3 boxes with FreeBSD-4 that won't easily upgrade but yes: > Note that src-5 hasn't changed for three years, and src-4 for even > longer. (The updates on 9/23/2012 were just header changes due to > switching from cvs to svn.) Tracking 4 & 5 is a moot procedure, it might as well stop if consuming needed resources. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. From owner-ctm-users@FreeBSD.ORG Fri Jan 11 16:58:28 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DEC408C0 for ; Fri, 11 Jan 2013 16:58:28 +0000 (UTC) (envelope-from daeron@optushome.com.au) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFB26FB for ; Fri, 11 Jan 2013 16:58:27 +0000 (UTC) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id r0BGwKYZ028418 for ; Sat, 12 Jan 2013 03:58:20 +1100 Received: from cirth.localnet (pa49-176-67-16.pa.nsw.optusnet.com.au [49.176.67.16] (may be forged)) (authenticated sender daeron) by mail12.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id r0BGw8Va031782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 12 Jan 2013 03:58:12 +1100 From: Andrew To: ctm-users@freebsd.org Subject: Size limit for ctm pieces Date: Sat, 12 Jan 2013 03:58:01 +1100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-STABLE; KDE/4.8.4; i386; ; ) X-KMail-Markup: true MIME-Version: 1.0 Message-Id: <201301120358.01405.daeron@optushome.com.au> X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.0 cv=Or8XUFDt c=1 sm=1 a=XbvlWfARY4YA:10 a=lojdg71KAAAA:8 a=-yMXj1CvV-sA:10 a=MyqG83uGywnVvJgNqUUA:9 a=CjuIK1q_8ugA:10 a=SSmOFEACAAAA:8 a=a_O9Sf58eT-pvoSwnqkA:9 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=VKcSgxPsRyizQNSSMBI9Iw==:117 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 16:58:28 -0000 With a 100Kbyte limit the ctm server can gag for several days when it has to send a 1Mbyte or larger delta. For example when I requested ctm-src-9 two days ago, 24 hours later I received pieces 5 & 6 of 15 pieces, and another day later I've recieved pieces 7 & 8 of the 15 pieces. At this rate it will be another four days before it completes src-9.0550 and is able to then proceed to src-9.0551 and the rest in the queue I would suggest a 3,000,000 byte limit for ctm pieces should be safe and would be more realistic today given a mobile phone typically gets 300Kbyte/sec these days and most mail servers seem to have been set to 10Mbyte size limits (as oppose to the standard 5Mb limit of a few years ago). From owner-ctm-users@FreeBSD.ORG Fri Jan 11 17:29:15 2013 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 44B4ED2E for ; Fri, 11 Jan 2013 17:29:15 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 1364A81F for ; Fri, 11 Jan 2013 17:29:14 +0000 (UTC) Received: from [128.206.184.213] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.6/8.14.6) with ESMTP id r0BHTDLl077996; Fri, 11 Jan 2013 11:29:13 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <50F04BE9.3080705@missouri.edu> Date: Fri, 11 Jan 2013 11:29:13 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130111 Thunderbird/17.0.2 MIME-Version: 1.0 To: Andrew Subject: Re: Size limit for ctm pieces References: <201301120358.01405.daeron@optushome.com.au> In-Reply-To: <201301120358.01405.daeron@optushome.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ctm-users@freebsd.org X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jan 2013 17:29:15 -0000 On 01/11/13 10:58, Andrew wrote: > With a 100Kbyte limit the ctm server can gag for several days when it has to > send a 1Mbyte or larger delta. > > For example when I requested ctm-src-9 two days ago, 24 hours later I > received pieces 5 & 6 of 15 pieces, and another day later I've recieved pieces > 7 & 8 of the 15 pieces. At this rate it will be another four days before it > completes src-9.0550 and is able to then proceed to src-9.0551 and the rest in > the queue > > I would suggest a 3,000,000 byte limit for ctm pieces should be safe and > would be more realistic today given a mobile phone typically gets 300Kbyte/sec > these days and most mail servers seem to have been set to 10Mbyte size limits > (as oppose to the standard 5Mb limit of a few years ago). The problem was at my end. The computer should send one piece every hour. But I had forgotten to set up this hourly sending for src-9!!! I fixed it now, and you should start to receive the pieces hourly. However - there is also a ctm-src-9-fast mailing list, where you will get all the pieces at once. Thank you for bringing this issue to my attention, and my apologies for not setting up src-9 properly. Stephen