Nis Martensen wrote: > Without this, the CGI was creating web pages that had no > other-read permissions, (which meant that apache couldn't > serve them unless they happened to belong to the same group > as the apache process (www-data I believe?)).
This has been requested a few times before, my problem with doing this is that programs that ignore umask settings tend to violate least suprise. You've managed to avoid some suprises by putting the umask in the wrapper, but there are still some left. If someone has an ikiwiki wrapper that they just run at the command line to refresh a wiki, or a ikiwiki wrapper for w3mmode, and they use a special umask to open up or restrict access to files, they will be suprised to find their umask is ignored. I suppose it could be implemented as an option. Although wouldn't it be better for apache itself to have an option for setting the umask? I'm sure there are other cgi scripts that write files with unexpected modes when apache inherits an unusual umask. -- see shy jo
signature.asc
Description: Digital signature
