From owner-cvs-all  Sun Oct 31 20:58:20 1999
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5FE9F152BB; Sun, 31 Oct 1999 20:57:44 -0800 (PST)
	(envelope-from julian@FreeBSD.org)
Received: (from julian@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id UAA26060;
	Sun, 31 Oct 1999 20:57:44 -0800 (PST)
	(envelope-from julian@FreeBSD.org)
Message-Id: <199911010457.UAA26060@freefall.freebsd.org>
From: Julian Elischer <julian@FreeBSD.org>
Date: Sun, 31 Oct 1999 20:57:44 -0800 (PST)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/kern vfs_syscalls.c src/sys/sys mount.h
         src/bin/df df.1 df.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

julian      1999/10/31 20:57:44 PST

  Modified files:
    sys/kern             vfs_syscalls.c 
    sys/sys              mount.h 
    bin/df               df.1 df.c 
  Log:
  Most modern OSs have the ability to flag certain mounts as ones to
  be ignored by default by the df(1) program.  This is used mostly to
  avoid stat()-ing entries that do not represent "real" disk mount
  points (such as those made by an automounter such as amd.)  It is
  also useful not to have to stat() these entries because it takes
  longer to report them that for other file systems, being that these
  mount points are served by a user-level file server and resulting in
  several context switches.  Worse, if the automounter is down
  unexpectedly, a causal df(1) will hang in an interruptible way.
  
  PR:		kern/9764
  Submitted by:	Erez Zadok <ezk@cs.columbia.edu>
  
  Revision  Changes    Path
  1.140     +3 -3      src/sys/kern/vfs_syscalls.c
  1.83      +4 -2      src/sys/sys/mount.h
  1.17      +5 -2      src/bin/df/df.1
  1.22      +11 -6     src/bin/df/df.c



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message