On Tue, 2005-06-14 at 17:29, Stephen Turner wrote: > On Tue, 14 Jun 2005, George Klein wrote: > > > I'm experimenting with cache files at the moment. When I create one it > > has 0600 permissions although I would like it to have 0640 and I have my > > umask set to 027. > > > > Is there some configuration I've missed or do I just have to do a chmod > > after creating the cache. If analog isn't intended to use umask could > > someone please explain why. > > > > Analog doesn't do anything special with umasks (after all, it's supposed to > be OS independent as far as possible). It just writes to the file. The OS > determines the file permissions. Maybe you're running analog as a different > user in a cron job, not as yourself?
For the benefit of any future browsers, I've found the cause: Every test I tried pointed to this being specific to analog so I eventually gritted my teeth and looked at the source code. I found that analog creates the cache file with mode 600 which means that no other permissions can be added by any setting of umask. Now I understand what's happening, I'm content to use chmod in my script to get the permissions I want. +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
