Re: umask wierdness

* Thus wrote Bret Hughes (bhughes@elevating.com): > I have found a funky situation that I am trying to figure out if it is > bug or not: > > I see this behavior on both redhat 9 and fedora running > > php 4.3.4 > httpd(apache) 2.0.48 > > calling umask(0002) in a script leaves the httpd process with a umask of > 2 after exit so that the next process to hit that process gets the new > umask. in other words the environment does not revert to default as the > umask() docs say it should. This does not happen on my 7.3 box running > apache-1.3.27-2 > php-4.1.2-7.3.6 > > I found this chasing a rabbit trail of a bug. This is kind of sneaky > since it only changes the umask for the single httpd process it hits. > multiple calls to umask(0002) will change every process it hits. This set up works perfectly fine for me, umask is reset to original value after php dies so all my checkumask.sh output results with 18. System: FreeBSD, apache 1.3.29, php5. Looking at the php source code, it looks like all its doing is calling the system's umask(), which leads me to belive its an issue with either the OS or apache. You might want to ask internals@php.net about this they might be able to help you a little more about this. Curt -- "I used to think I was indecisive, but now I'm not so sure."