[PATCH][saslauthd] cyrus-sasl-2.1.10/saslauthd credential caching

[Igor Brezac]

On Wed, 15 Jan 2003, Jeremy Rumpf wrote:

> On Tuesday 14 January 2003 23:36 pm, Igor Brezac wrote:
> > Jeremy,
> >
> > This stuff looks great and with a limited user sample (10) the performance
> > improvement was almost 100 fold.  Keep in mind, this is my first crack at
> > it.  I am using Solaris 9.  I am getting the following error
> >
> > # ./saslcache -s
> > could not attach shared memory segment: 1200
> > shmat: Invalid argument
> >
> > It is likely I need to adjust shared memory params.  I'll let you know
> > what I find.
> >
> > One more note, can you make the changes against the  cvs version?
> >
> > -Igor
> >
>
>
> Ok, I've set things up on a Solaris 8 machine for testing. After a few tweaks,
> things appear to be working ok. One thing though, it seems that the maximum
> shared memory segment size on Solaris is 1M by default. Solaris users will
> have to tweak their system settings if a larger cache is desired. Due to
> this, I've set the default cache size to under 1M (down from ~4M). This way
> saslauthd will always start with the cache enabled under default
> circumstances.
>

Solaris 9 defaults to 8M: http://docs.sun.com/db/doc/806-7009/6jftnqsj7?a=view
I would think that 1M is a fairly generous cache size unless you have
millions of users.  This is a 'short lived' cache mechanism where a
username is most likely to be reused shortly there after.

> Changes at:
>
> ftp://ftp.net.ohio-state.edu/pub/users/jrumpf/cyrus-sasl/cyrus-sasl-2.1.10-cache-2.patch
>
> Or fully patched source at:
>
> ftp://ftp.net.ohio-state.edu/pub/users/jrumpf/cyrus-sasl/cyrus-sasl-2.1.10-cache-2.tar.gz
>
>
> I'll work on getting a diff against current cvs as well....
>

Cool.  I'll wait for your cvs diff.  Do you use any kind of locking
mechanism such as semaphores or messages?

-- 
Igor