In an eZ Publish clustered environment:

C:\sites\trunk_cluster>php bin/php/ezcache.php --clear-id=template-block --verbose --debug=all --purge

It doesn't remove cache blocks.

SQL executed:

DELETE FROM ezdbfile WHERE name LIKE 'var/ezwebin_site/cache/template-block/%' AND mtime < 1219923528 LIMIT 100

The number mentioned in the query above is the current value of the global-template-block-cache expiry key.

The query only removes cache blocks that are expired from the database.

So first we should expire by running the script without the --purge option:

C:\sites\trunk_cluster>php bin/php/ezcache.php --clear-id=template-block --verbose --debug=all

Now the timestamp of the expiry key will be adjusted. And the next run with the --purge option will remove all cache blocks from the database.

This is currently not clear from the documentation at http://ez.no/doc/ez_publish/technical_manual/4_0/reference/scripts/generic/ezcache_php.

First we need to question of course if it's unexpected behavior, so a bug, or only a documentation issue.