https://bugzilla.wikimedia.org/show_bug.cgi?id=48818

Tim Landscheidt <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #1 from Tim Landscheidt <[email protected]> ---
http://marc.info/?l=grid-engine-users&m=112448326118257&w=2 (NB: from 2005, but
I didn't find anything more current) suggests that the permissions are
hardcoded in SGE.

But a small test ("jsub true"; "chmod 600 ~/true.{err,out} && jsub true")
showed that SGE doesn't change permissions if the error and outputs file
already exist.  So technically it seems to be possible to preemptively touch
the error and output files.

However, a quick fix has the potential to severely disrupt jobs of users like
me :-) who point "-o" to a directory.  So I'll think about a patch that
considers these different use cases till next week.

My initial idea would be:

If the error and/or output file do not exist:
  If the user supplied a "-umask" option:
    "umask (oct ($umask));"
  Else:
    If we are a tool account:
      "umask (0007);"
    Else:
      "umask (0077);"
  If $stderr:
    Open and close error and output files.
  Else:
    Redirect STDOUT/STDERR to them.

This would provide a sensible default (if a user has no opinion, make the
output  rw------- for users and rw-rw---- for tools), doesn't override the
user's action outside of SGE (i. e., "chmod") and allows them to specify
permissions for new logs in a clear way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to