From owner-freebsd-questions@FreeBSD.ORG  Fri Jun  4 07:59:21 2010
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E7BF71065670
	for <questions@freebsd.org>; Fri,  4 Jun 2010 07:59:21 +0000 (UTC)
	(envelope-from fbsd1@a1poweruser.com)
Received: from mail-03.name-services.com (mail-03.name-services.com
	[69.64.155.195])
	by mx1.freebsd.org (Postfix) with ESMTP id D10D88FC23
	for <questions@freebsd.org>; Fri,  4 Jun 2010 07:59:21 +0000 (UTC)
Received: from [10.0.10.3] ([202.69.173.90]) by mail-03.name-services.com with
	Microsoft SMTPSVC(6.0.3790.3959); Fri, 4 Jun 2010 00:59:21 -0700
Message-ID: <4C08B252.8010008@a1poweruser.com>
Date: Fri, 04 Jun 2010 15:59:14 +0800
From: Fbsd1 <fbsd1@a1poweruser.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "questions@freebsd.org" <questions@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Jun 2010 07:59:22.0245 (UTC)
	FILETIME=[D7ADCB50:01CB03BB]
X-Sender: fbsd1@a1poweruser.com
Cc: 
Subject: /var/empty has schg flag turned on. Why?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jun 2010 07:59:22 -0000

Why does the base RELEASE have schg flag turned for the /var/empty 
directory?

Is that directory really used for anything?

Is this a release build problem?