There must be a bug somewhere because I had EMBPERL_DEBUG = 0 and was getting
errors about not being able to write to /tmp/embperl.log.
This is with v 1.2b4 I believe so if this has changed recently that may be why
I got the errors.
On 20-Jan-00 Gerald Richter wrote:
That's what I thought.
There must be a bug somewhere because I had EMBPERL_DEBUG = 0 and
was getting
errors about not being able to write to /tmp/embperl.log.
This is with v 1.2b4 I believe so if this has changed recently
that may be why
I got the errors.
This didn't have change recently, but it is possible
Jason,
Using both 'EMBPERL_LOG /dev/null' and 'EMBPERL_DEBUG 0' will do the trick.
Without redirecting EMBPERL_LOG, embperl will always try to open
/tmp/embperl.log on its first use. I consider this a bug and a security hazard
(writing anything blindly to /tmp can have potentially lethal side
That's what I thought. Setting 'EMBPERL_DEBUG 0' should really turn off any
kind of logging including even trying to open the log file.
On 19-Jan-00 Christian Gilmore wrote:
Jason,
Using both 'EMBPERL_LOG /dev/null' and 'EMBPERL_DEBUG 0' will do the trick.
Without redirecting EMBPERL_LOG,
