From owner-cvs-all@FreeBSD.ORG Sat Jul 3 17:54:12 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EB8916A4CE; Sat, 3 Jul 2004 17:54:12 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B1943D48; Sat, 3 Jul 2004 17:54:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from samsco.org (junior-wifi.samsco.home [192.168.0.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i63HwVJ0082966; Sat, 3 Jul 2004 11:58:31 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40E6F2B2.4060307@samsco.org> Date: Sat, 03 Jul 2004 11:53:54 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <20040703171116.GC17270@green.homeunix.org> <52210.1088874758@critter.freebsd.dk> <20040703172003.GD17270@green.homeunix.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Brian Fundakowski Feldman cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/kern sched_ule.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 17:54:12 -0000 Bjoern A. Zeeb wrote: > On Sat, 3 Jul 2004, Brian Fundakowski Feldman wrote: > > >>It's safe to say it's working in his perforce branch; dooes anyone know >>why http://perforce.freebsd.org can't be used to browse them anymore >>(ECONNREFUSED)? > > > security reasons I got told last time I asked. > The p4db back-end is a large security risk. Anyways, I'm sure that John will look at this once he's home from USENIX in a few hours. Net access got cut off early there last night so I doubt that he's had a chance yet to see what went wrong. Scott