The reason it doesn't clean up when you restart is the shared memory that it uses for storing the cache. You could have a separate cache per process instead. (There's a parameter to control this.) You could also change the module to use something better like Cache::Mmap instead.
If no one logs in for a while and the data expires, the first time someone performs an action on the server it will still have stale data, but at the end of that request it will be cleared. So, you could say something like "if you've changed your password and your new login doesn't work, just try it again and it will." | [reply] |
I have a different behaviour here:
My user can't just login again as you said, because the cache is not cleaned for user X even if user X logs in after the cache's expiration. I have to make user Y login, so that the cache is clear for Mr.X ... Wich is why I posted the question in the first place.
In theory, if I had only one user, then his cache would never be renewed ( if you follow me so far). Strange, no?
| [reply] |