On 05/22/12 21:07, James Cammarata wrote:
> And I think the solution would be something like the attached
patch,
> using os.open() with mode parameter to avoid os.umask.
One fix: shouldn't the mode be 0600 rather than 0200? As is, it's
creating the file with write permission only and no read.
Yes, I think "0600" is the right permission.
I used "0200" just because /var/lib/cobbler/.mtime on my
cobbler server was write-only.
Also please note the patch changes only 2 callers of umask,
which I suspect could be called from threads.
It might be good idea to change other places as well.
Thanks,
--
Jun'ichi Nomura, NEC Corporation