The fscache module creates a directory under misc/fscache called "D2." I cannot FTP to the contents of this directory and view its contents. This disturbs me. I imagine that the fscache module isn't properly setting permissions when it creates various folders. Can this be corrected? My fear is that this folder will become over filled with pdf files and unecessarily take up space on the site. I should at least be able to see how it's working!

Comments

gordon’s picture

gordon CreditAttribution: gordon commented

This is actually by design. The contents of the fscache directory is basically a blob of unknown files. The permisions are actually set to that of the web server user. This means that you cannot use fscache to upload files for an attach on the system.

bomarmonk’s picture

bomarmonk CreditAttribution: bomarmonk commented

Is there a way to overide this behavior? If my users (only a select group) are uploading .pdf files, what's the need to lock down the folders. I guess I would still like to know more about how this module works. Thanks for any further explanation.

gordon’s picture

gordon CreditAttribution: gordon commented

there is nothing really human readable in that directory. the actual file names have not relationship with the uploaded filenames. The names themselves are just an random hex number that have been manipulated to try and give an even spread over a set of directories.

Basically from a global pov, I want to lock down these directories as much as possible.