Hi Wayne,
As far as I can tell from the code you posted, the actual code that opens the file and writes to it is probably somewhere in the SaveUTF method.
The two examples I showed can be used to check the umask from the command line like so:
$ umask 0022 $ perl -e 'printf "%04o\n", umask;' 0022
Or, the best thing is probably to put the statement printf "%04o\n", umask; somewhere in your Perl script, maybe something like warn sprintf("umask is %04o\n",umask); so that it's printed to STDERR.
Update: In your OP you wrote "I must note here that an accompanying file generated by the application saves with 0644 permissions." That makes it a little less likely to be a umask problem; perhaps the application uses sysopen with explicit perms set. But without having the code to look at these are all guesses.
Hope this helps,
-- Hauke D
Update: Replaced "an explicit mode" with "explicit perms" since that's the terminology used in sysopen.
In reply to Re^3: File permissions problem (updated)
by haukex
in thread File permissions problem
by wdhammond
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |