keys issues in filebased cache backend

[san@…]

on my fedora 19 system with django version 1.6.1 final I have an error while try to set and get keys from
different sessionś : I add custom command to the django manage which set key in django.core.cache, this work is done by apache user. After that when apache server is runing and operate from apache user I can´t read that key. I found that file based backend give right file name and abs path to the pickle file but that file for some reason have different inode number when I read it in the apache operate mode and from django shell from apache user.

thx

[Russell Keith-Magee]

This sounds very odd. Django's file framework is just opening and closing files using normal Python file semantics. The worst problem I'd expect to see would be related to cache file ownership and/or permissions. I can't think of anything that would cause issues at the *inode* level.

I also use the file cache myself, and I've never seen anything like the sort of problems you've described.

I'm not denying that you're having a problem, and that it's inode related -- but we're going to need a lot more specific information if we're going to reproduce this (I'm guessing down to the level of OS patch levels and hardware, since inodes aren't something that Django normally has any access to).

Closing needsinfo -- please reopen if you can provide more information.