>}This was pretty bad with the V4 database code, but _if_ you use V5 and
>}you use the btree database backend, then this is a lot better. And one
>}of these days I'm going to get incremental database updating done ....
>
> Hmmm, we've been using Kerberos since 1990 and
> we currently have 38,608 principals (36,240 users).
>
> All this time we've never had a hitch with V4
I think it's all in how often you want to propagate your database.
With MIT Kerberos, the database is locked during a dump, which
means users can't change their passwords during that time. If you
have a lot of principals, and you want to propagate your database
twice an hour, then you'll have a problem :-)
That's assuming, of course, that your users actually _change_ their
passwords ...
--Ken
