File permission mask
Brought to you by:
macdome
Menu
▾
▴
#16 File permission mask
From email:
OpenAG appears to ignore/override my umask
(22) and default permissions. All songs are
downloaded into a ~/tmp directory which has
permissions set to 755. While OpenAG downloads
a file the file's permissions are set to 600
(presumably by OpenAG.) Once the transfer is
complete OpenAG moves the file from the ~/tmp
directory to a completed directory which has
permissions set to 755 also. I would therefore
expect all mp3s in that completed directory to have
permissions of 644 accordingly. Interestingly
enough they don't. They're magically changed from
600 to 660 instead.
I've got a script running (cron'd) every minute to
change permissions in the completed directory,
but am wondering whether I can otherwise change
OpenAG's behavior or if this behavior is even
intentional.
<comments>
This is old, and might be fixed, but I doubt it.
Should be a trivial fix.
Logged In: YES
user_id=151346
From a second email:
### EXAMPLE ###########################
There are two folders OpenAG uses, one for
incomplete transfers and the other for completed
transfers as follows:
~/incomplete_openAG/
~/downloads_openAG/
Permissions for these directories are as follows:
drwxr-xr-x 8 cibo staff 228 Feb 28 05:47
incomplete_openAG
drwxr-xr-x 2 cibo staff 24 Feb 28 06:15
downloads_openAG
When a file is in progress it shows up in ~/
incomplete_openAG/ with the following permissions:
-rw------- 8 cibo staff 228 Feb 28 05:47
some_song.mp3
600 just like you said. Once the transfer is complete
OpenAG moves the file to ~/downloads_openAG/
where they end up with the following permissions:
-rw-rw---- 8 cibo staff 228 Feb 28 05:47
some_song.mp3
For some reason they end up as 660 files, not 644 as I
would like and as you indicate OpenAG should be
doing.
Now, if I create a new file in that directory simply by
using 'touch' at the commandline it shows up as:
-rw-r--r-- 1 cibo staff 0 Mar 1 20:20 test_file
644, which is expected b/c I am the owner of the
directory with full permissions, and my umask is 022.
######################################
Don't get me wrong-- I'm not saying definitively that
OpenAG is the problem. Rather, I was merely inquiring
whether this was OpenAG's standard/expected
behavior, and from you've told me it definitely is not.
It seems like something is overriding my permission in
that directory but I do not have any scripts running,
neither as root or as myself. So this is a bit bewildering
to me but not really your problem after all.
Also, I didn't mean to suggest there is a standard
convention per se, just that given my specific umask
working in conjunction with the directory permissions
should yield a predictable result. Since neither my
umask or directory permissions are out of the norm,
one could argue that these are somewhat "standard."
I appreciate your attention and your goodwill to help. If
this sounds entirely like a problem on my end, I
apologize for wasting your time. If not, let me know what
else I can do to help troubleshoot.
Thanks,
roman