From owner-freebsd-current Tue Feb 23 1:12:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B6F5F110E8 for ; Tue, 23 Feb 1999 01:12:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA60552; Tue, 23 Feb 1999 09:04:48 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 23 Feb 1999 09:04:48 +0000 (GMT) From: Doug Rabson To: Bruce Evans Cc: mike@smith.net.au, romanp@wuppy.rcs.ru, current@freebsd.org Subject: Re: Problems with nfsstat and dynamic OID In-Reply-To: <199902220752.SAA01270@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Feb 1999, Bruce Evans wrote: > >I fixed this a while back to use sysctlbyname, as it should have been > >done. Bruce subsequently backed it out (bad idea, IMO). > > You only worked around the previous breakage of vfs sysctls for the > statically configured case. The dynamically configured case was more > fundamentally broken (sysctls were not wired at all). Other applications > that use vfs sysctls, e.g., mountd(8), remained broken in all cases. Even then, only NFS' sysctls were 'fixed' to use vfc_typenum as their oid numbers. Other filesystems with sysctls such as ufs were still 'broken'. It is possible to change vfs_register so that it hacks the vfc_typenum into any oid it finds under 'vfs.' with the right name. I prefer just changing the supported mode of access to sysctlbyname(). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message