[Zope-Coders] new zLOG

[Toby Dickenson]

On Tuesday 26 November 2002 1:41 pm, Guido van Rossum wrote:

> I propose that there be some interface where Zope (or any setuid
> program) can call e.g. zLOG.initialize_later() immediately after
> importing zLOG, and if this hasn't been called by the time LOG() is
> called for the first time, the first LOG() call calls initialize().

I dispute the need for this interface.

It should be easy to find potential calls to LOG before such a program dr=
ops=20
root. If so, it should also be easy to disable those calls in the=20
application, rather than at ZLOG level.

If it is not easy to find out exactly what your program does before dropp=
ing=20
root privelidges then you already have bigger problems.

> This new interface could be called from z2.py.

That would solve a 'problem' that only exists due to the stupidity of the=
=20
stupid log file. However it would be a disservice to all other sensible f=
orms=20
of logging such as syslog (Ive not looked at the new logging package, I h=
ope=20
it has some other choices).


(Yes, I agree the stupid log file is sometimes useful, and you dont alway=
s=20
care about its insecurity. I assert that you wont be starting Zope as roo=
t in=20
all such cases)