From owner-freebsd-questions@freebsd.org Sat Aug 13 10:28:46 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D1E4BB7395 for ; Sat, 13 Aug 2016 10:28:46 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: from mail.irealone.com (fawn.irealone.com [IPv6:2001:1af8:4010:a07b:10::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A9BB1721 for ; Sat, 13 Aug 2016 10:28:46 +0000 (UTC) (envelope-from vlad-fbsd@acheronmedia.com) Received: by mail.irealone.com (Postfix, from userid 1002) id 2B64A60B4B; Sat, 13 Aug 2016 12:28:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=acheronmedia.com; s=mail; t=1471084123; bh=tvhHp6mQJ0TpTyl0LFgUyRT51CjvpYgV6N44iUJG9r0=; h=To:Subject:Date:From:From; b=YAt+UnLLwYKvyjlY1sqwTpjOlADi07k9x3yYbX7rTPNH2bH/dbABRdy4AKSvfWYLb Lyb4gbvVd0gGPylSkITJEoUDNEGxNeOEkTaBE0G0aeHPN/6N1PS+rAD2iHSecggux/ 9MEMgyN/0hwZtHn3EESjywRcO5UN2UXSn+CDnxiQ= To: freebsd-questions@freebsd.org Subject: freebsd-update's "Fetching patches" phase? X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 13 Aug 2016 12:28:43 +0200 From: "Vlad K." Organization: Acheron Media Message-ID: <823dd643595a5be72671fd5d9c7199b0@acheronmedia.com> X-Sender: vlad-fbsd@acheronmedia.com User-Agent: Roundcube Webmail/1.1.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Aug 2016 10:28:46 -0000 Hello list, what's the freebsd-update "Fetching patches" phase for? I've set up a central reverse proxy cache for all my servers to speed things up, and looking at how it behaves I've noticed that the "Fetching patches" phase is resulting with 404s for each link attempted. Now, I don't know if this is because it's still not final -RELEASE version, but it does look incredibly inefficient. Upgrading from -BETA4 to -RC1 queried over 9000 (heh) URLs all of them returning 404s. I've configured my proxy to cache 404 too so the servers just blast through that local cache after the first server is done. -- Vlad K.