Date: Fri, 14 May 1999 09:18:41 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Roar Thron?s <roart@nvg.ntnu.no> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: large master.passwd Message-ID: <19990514091840.A18547@dan.emsphone.com> In-Reply-To: <Pine.GS4.4.10.9905141040560.875-100000@phoenix.nvg.ntnu.no>; from "Roar Thron?s" on Fri May 14 11:12:18 GMT 1999 References: <XFMail.990513222354.gbuchana@home.com> <Pine.GS4.4.10.9905141040560.875-100000@phoenix.nvg.ntnu.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 14), Roar Thron?s said: > On a site with 20k users in the master.passwd, and where NIS is not > trusted, the master.passwd is distributed to each workstation. The > pwd.db and spwd.db are sized around 10Mb. > > Sometimes, those .db files get corrupt. I suspect it has something to > do with the machines being reset etc before the sync is finished. > (The machines are dual-boot, and there are a lot of users around.) > > I did some patching, and have not seen corrupted .db-files since. > > So how usable is this patch? > Worth intregrating? > - 2048 * 1024, /* cachesize */ > + 8192 * 1024, /* cachesize */ Cachsize is already adjustable via the -s commandline switch. > + /* sync may be wise > + -roart */ > + sync(); How about an fsync() of only that file? (I don't remember whether fsync flushes metadata though) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990514091840.A18547>