>>>>> "Curt" == Curt Arnold <[EMAIL PROTECTED]> writes:
Curt> On Aug 1, 2007, at 2:10 AM, Michael Schmitz wrote:
>> I disussed almost the same issue with the log4perl guys as the
>> problem Christian described is actually a major problem in our
>> project. I think it would be a great idea to permit
>> specification of the file mode via the configuration.
Curt> I asked for comments on log4net-dev
Curt> (http://marc.info/?l=log4net- dev&m=118598739032116&w=2) and
Curt> didn't get much insight beyond don't have multiple processes
Curt> hit the same log file (which is a good and true statement).
Curt> log4net has the idea of a nested securityContext where you
Curt> can specify that logging would be done as a particular user
Curt> (which would be one way around the file permissions issue),
Curt> but I have no direct experience with it.
Curt> Is there an archive of your discussion with log4perl?
No, I don't think so. My dicussion regarding an initialization issue
are in the archive, but this one not.
Curt> Since umask and chmod both seem to be provided as standard
Curt> PHP library functions, then it seems that PHP is responsible
Curt> for emulating or stubbing them on Windows or other platforms
Curt> with different file permission models.
Curt> I would suggest that if the user does not specify a umask or
Curt> chmod value, then umask or chmod not be called. Looking at
Curt> the original patch, it seemed like it did not have a concept
Curt> of an unspecified umask. Since both umask and chmod have
Curt> warnings, I'd suggest implementing them both and the user is
Curt> responsible for making the right choice (and if they
Curt> specified neither than neither function is called).
This sounds like a good suggestion to me.
