From owner-freebsd-chat Tue Aug 27 22:43:48 1996 Return-Path: owner-chat Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA02322 for chat-outgoing; Tue, 27 Aug 1996 22:43:48 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA02294; Tue, 27 Aug 1996 22:43:43 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id BAA26445; Wed, 28 Aug 1996 01:43:39 -0400 (EDT) Date: Wed, 28 Aug 1996 01:43:39 -0400 (EDT) From: Brian Tao Reply-To: FREEBSD-CHAT-L To: FREEBSD-CHAT-L cc: FREEBSD-ISP-L Subject: Another pointless contest... gigantic passwd files? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't have any FreeBSD servers that have 400-day uptimes (although our Majordomo server is at 102 days now), but I figure one of our servers may have the largest passwd file around. :) # cd /etc # ls -ls *passwd *pwd.db 7632 -rw------- 1 root wheel 7806209 Aug 27 18:16 master.passwd 5936 -rw-r--r-- 1 root wheel 6063368 Aug 27 19:02 passwd 38936 -rw-r--r-- 1 root wheel 41750528 Aug 27 18:58 pwd.db 43752 -rw------- 1 root wheel 73437184 Aug 27 19:02 spwd.db # wc -l passwd 102531 passwd Generating the db files with a pwd_mkdb modifed with cachesize set to 64MB cache took about 45 minutes on a P133 while handling mail and primary DNS (named was occupying about 30MB itself). It was swapping rather heavily, and I think I can get the time to under half an hour on an unloaded system with 128MB of RAM. Now to figure out what we're going to do with NFS's 16-bit uid's and the best way to handle mail for 100,000 users... (replies set to freebsd-chat) -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"