On Tue, Nov 10, 2009 at 11:14:40AM -0600, John Washington wrote:
> Our backend was last counted at over 200,000 principals and the only
> noticeable
> impact (at this time) is that propagation time is around two minutes.
My previous experience was with ~100K principals, and indeed, it scales
fine
On 10 nov, 22:21, Ken Raeburn wrote:
> On Nov 10, 2009, at 12:14, John Washington wrote:
>
> > Our backend was last counted at over 200,000 principals and the only
> > noticeable
> > impact (at this time) is that propagation time is around two minutes.
>
> Have you looked into the new (Sun-contr
On Nov 10, 2009, at 12:14, John Washington wrote:
> Our backend was last counted at over 200,000 principals and the only
> noticeable
> impact (at this time) is that propagation time is around two minutes.
Have you looked into the new (Sun-contributed) incremental propagation
code in 1.7?
Ken
Our backend was last counted at over 200,000 principals and the only noticeable
impact (at this time) is that propagation time is around two minutes.
* garnett [2009-11-08 22:40]:
> Hi all,
>
> In our University I wish to centralize authentication in a Linux MIT
> KDC. This operation will spawn
On Nov 8, 2009, at 09:20, garnett wrote:
> In our University I wish to centralize authentication in a Linux MIT
> KDC. This operation will spawn a KDC with about 30 000 principals. Is
> it a problem for Kerberos MIT implementation ? We will run the 1.6
> version bundled with Debian Lenny.
>
> Is th
Hi all,
In our University I wish to centralize authentication in a Linux MIT
KDC. This operation will spawn a KDC with about 30 000 principals. Is
it a problem for Kerberos MIT implementation ? We will run the 1.6
version bundled with Debian Lenny.
Is there a need for tricks to handle such a data
