Well, if you are worried about intentional collisions, then you should use umask.

If you are worried about accidental collisions ( i.e. somebody running the same script by accident) then it sounds like you need to implement locking. You could take a look at Proc::Pid_File.

I'm terribly sorry but I also should have mentioned in my original post that this is running on a ActiveState Win32 system.

-Nitrox

Why would you want to create a separate script that writes to the same namespace?

Just don't do it, or write to a unique namespace.

So what's it matter if information gets overwritten (what are you using this for, caching or what)?

Don't confuse FileCache with a database. It's used for caching/sharing data.

or use a nice flocking scheme if you can, or even a simple semaphore based solution separate from the FileCache module

or better yet, why don't you (or we, i'll help) create a Cache::FileCache::FLOCKED which does simple semaphore based flock'ing?

um, forget that. If you're getting collisions, prevent them. Make your keys sufficiently unique (appending time() works well). Just what exactly are you storing there?

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.

I'm fully aware of the usage of FileCache, I'm using it to share data between two separate processes. I have one 'always-running' process that reads,resets,and acts upon "flags" created by separate 'short-running' scripts.

-Nitrox

Nitrox:

I'm liking this thread, and it was interesting to hear why you are using File::Cache. Just a couple of things:

1. Create a group for your 'short running scripts' and long running daemon to be a part of (this is probably possible in Win32 :).) Have the File::Cache write it's hierarchy to a place where only people in the group can read/write.
2. Use a key, and encrypt the cache values. If you don't care if people can read through your keys, then this can add a smidge of integrity. That is, agree on a 'password' for all data being written to the key and then use an symmetric Crypt:: module.

Hope that's helpful...Good luck!

By the way, did you notice that on the File::Cache actually recomends using Cache::Cache instead? Hm...

Kurt

umask sounds like the way to go. Just make sure your process runs under an account others can't login to.