From owner-cvs-ports Thu Apr 6 00:04:31 1995 Return-Path: cvs-ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA12820 for cvs-ports-outgoing; Thu, 6 Apr 1995 00:04:31 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA12812 ; Thu, 6 Apr 1995 00:04:28 -0700 Received: from vinkku.hut.fi (vinkku.hut.fi [130.233.245.1]) by time.cdrom.com (8.6.11/8.6.9) with ESMTP id AAA11001; Thu, 6 Apr 1995 00:04:23 -0700 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id KAA26897; Thu, 6 Apr 1995 10:04:08 +0300 Date: Thu, 6 Apr 1995 10:04:08 +0300 From: Kai Vorma Message-Id: <199504060704.KAA26897@vinkku.hut.fi> To: "Justin T. Gibbs" Cc: "Jordan K. Hubbard" , "Rodney W. Grimes" , jkh@freebsd.org (Jordan K. Hubbard), CVS-commiters@time.cdrom.com, cvs-ports@time.cdrom.com Subject: Re: cvs commit: ports/net/sup/patches patch-ae In-Reply-To: <199504060638.XAA21740@estienne.cs.berkeley.edu> References: <11471.797149153@freefall.cdrom.com> <199504060638.XAA21740@estienne.cs.berkeley.edu> Reply-To: Kai.Vorma@hut.fi Sender: cvs-ports-owner@freebsd.org Precedence: bulk Justin T. Gibbs writes: > It doubles the number of stats needed to do an upgrade. It needs to Doubling stats on a client machine is not that much a problem. I am currently trying to do fast updatedb/locate program for our big fileservers and I am developing it using my own FreeBSD machine. The Slowest part is of course traversing filesystem. It took just some 80+ seconds to traverse my 1GB disk with some >30000 files and >1000 directories using brute force algorithm (stat for every file and directory) and about 70 seconds with 4.4BSD optimizations (using file info from struct dirent and onet stat() for each directory for other reasons). So making a few hundred or thousand stats on _client_ machine is not really that much an issue, IMHO. On a loaded server you probably want to avoid any stats possible. > be implemented another way and an option. I should be able to create > #sup files all I want if I choose to distribute them via SUP. You can do that. The special name for foo#sup is foo#sup#sup .. :-) > No, he should have used PATH_MAX or SUP's own STRINGLENGTH there I > would guess. SUP's STRINGLENGTH (see sup.h) has nothing to do with PATH_MAX (or whatever) so using it is no more better than 1024 (actually worse). Using MAXPATHLEN (or is it PATH_MAX fro posix systems?) would be the right way, I suppose. ..vode