Why is it OK for top to do it, but not pwd_mkdb? I probably end up updating my OS faster than I add users to my password file...
Tweak the cache to 32MB's, and never touch it again, regardless of how big your passwd file is... On Wed, 1 Sep 1999, Mike Smith wrote: > > > > > > Got tired of the dinky cachesize for pwd_mkdb, especially since vipw > > doesn't take advantage of the -u or -s options. > > > > So here a couple patches that make the cachesize tweakable from make.conf. > > > > Dramatically helps on those 10-15k line password files. > > > > I would appreciate it if somebody would at least consider committing > > this... > > No. Try for a patch that guesses how big the password file is (try > using stat()) and tunes the cache dynamically. > > Hardcoding this at _build_ time is not any sort of "right" solution. > > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msm...@freebsd.org > \\ -- Joseph Merrick \\ msm...@cdrom.com > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
