Re: [Wrapper-user] Re: How do we config the wrapper??

[Leif M. <le...@ta...>]

Martin,

Chow, Martin wrote:

> I just want to update what I did so far after receiving your 
> suggestions. I make sure that my log directory exist in the correct 
> relative location to the wrapper.exe. It turns out that I didn’t 
> specify the path correctly. In the wrapper.conf, I put in 
> wrapper.logfile=../log/wrapper.log. If I change this configuration to 
> wrapper.logfile=..\log\wrapper.log, I was able to create the wrapper 
> log file in the correct location (in my log directory and not the 
> default location). After the wrapper log is created and placed in the 
> correct directory, I was able to set the size and number of log files 
> (max log size and number of files before overwriting the existing log 
> file). Therefore, the problem seems to be the way I put in the ‘\’ or 
> ‘/’ for the log file configuration.
>
What platform are you using? Windows X? I have used the Wrapper on NT, 2000
and XP. In all cases using the forward slashes without any problems.

At any rate, I put in a fix for the 3.1.1 release to always convert '/' 
to '\' characters
in that property on Windows. Back slashes do not work on UNIX platforms and
it is important that the wrapper.conf file can be used on any platform 
unmodified.

> I do however have any similar problem in the configuration. I wonder 
> if you or anyone tries to disable the wrapper log file. According to 
> the documentation, if I give a blank value for wrapper.logfile 
> property, it will disable file logging. What do you mean by blank 
> value?? I try by setting (wrapper.logfile= ) and the wrapper just 
> default the wrapper log file to the default location. I also try erase 
> the entire (wrapper.logfile= ), but I still get a default log file in 
> the default location.
>
You have found a bug which it looks like was introduced way back in 
version 2.2.5.
Obviously not many people are interested in disabling the log file :-)

Anyway, you were doing this correctly:
wrapper.logfile=

The problem was that the Wrapper as is was trying to open a file called 
"". That
of course failed so it fell back to the default. This has been fixed and 
will be in the
3.1.1. release that is trying to get out the door. :-)

Cheers,
Leif