Grouper Users - Open Discussion List

[Scott Koranda <>]

Hi,

I have a fully patched Grouper 2.3 deployment.

None of the grouper.cache.properties files (for API, WS, or
UI) have been edited away from the default--they contain
nothing but comments.

I have not edited the grouper.cache.base.properties files, but
they may have been generated/touched during the upgrade
process to 2.3 from pre-existing ehcache.xml files. I had not,
however, edited the ehcache.xmlf files previously.

I wanted to compare the grouper.cache.case.properties files to
that from a clean download so I downloaded today's tarball
from

https://software.internet2.edu/grouper/release/2.3.0/grouper.apiBinary-2.3.0.tar.gz

but that tarball only contains ehcache.example.xml and
ehcache.xml files, not grouper.cache.base.properties or
grouper.cache.properties. 

Is that correct? Are the grouper.cache.base.properties and
grouper.cache.properties files generated on the fly during an
install?

Regardless, I am finding that ehcache is creating files in
/tmp that are not being deleted (after many days):

$ ls /tmp/ | grep grouper_ehcache | wc
    678     678   20340

Should some Grouper process be reaping those files, or is that
something I need to set up externally to Grouper?

Thanks,

Scott K