[Tickets #14258] Re: File based cache garbage collection broken

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14258
------------------------------------------------------------------------------
  Ticket           | 14258
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | File based cache garbage collection broken
  Warteschlange    | Horde Framework Packages
  Typ              | Bug
  Status           | Resolved
  Priorität        | 2. Medium
  Milestone        | Horde_Cache 2.5.3
  Patch            |
  Zuständige       | Jan Schneider
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2016-02-16 20:48) hat geschrieben:

We didn't lock the GC index in the old version either, so this  
couldn't be a reason for the regression. And we *do* lock the old  
index file while doing the migration, so the migration couldn't  
introduce this regression either.
Do you even see this after wiping the cache completely? This shouldn't  
be necessary of course, but with your current broken index files, you  
would have to do this anyway.