CM Synergy Clean Cache

[NickSteven]

Hi all,

I am getting problems with the CM Synergy cache filling up yet again
and with the clean_cache command which does not seem to do what the
documentation says (or at least what I think it says!) .

For example, if I look in my cache directory, I find a file: #26/36626
which has the following details from ls -l:

-r--r--r-- 1 ccm_root ccm_root 11256 Oct 6 2003 ./#26/36626

If I run ccm prop on the cvid "36626" and get a filespec back, the
full spec is: libDA_hooks.so=1.1.1:binary:1. This file is in the
released state.

If I run "finduse" on this filespec, I get a list of projects where
this file is used, and on that list I check the work area properties
i.e.:

Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build1 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build2 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build3 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build4 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build5 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build6 FALSE FALSE FALSE FALSE TRUE
FALSE ''
Project Maintain Copies Relative Time Translate
Modify Path
-------------------------------------------------------------------
GSP_SOURCE=5.0.mit.build7 FALSE FALSE FALSE FALSE TRUE
FALSE ''

So as you can see, all the projects where this file is used (which are
all in "released" state) do not have a work area maintained - as it is
my policy to switch this off before freezing the project.

Now, if I run clean_cache as follows:

ccm clean_cache -status released -c "-15:0:0:0"

I would expect this file to be removed from the cache as it fulfills
all the criteria - i.e. released state, and not in a work area, older
than 15 days etc etc. However it is not deleted.

I also tried running the same clean_cache command but with the -u
option specified but to no avail.

There are quite a few files like this in the cache.

Any thoughts?

Cheers,

Nick.