Re: [Wrapper-user] Wrapper on CruiseControl doesn't work

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

Marco,
This is because the Wrapper runs as the system user by default.  If you 
specify the
wrapper.ntservice.account property to be <username> then things should 
work as
you are expecting.
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-account.html

Cheers,
Leif

Marco Tedone wrote:
> I solved my problems thanks. It was a mixture of properties not set 
> properly and an error occurring during the unit tests, since, on my 
> system, the wrapper doesn't resolve Java system property user.home to 
> C:/Documents And Settings/<username> but it resolves to C:/Documents 
> And Settings/LocalService.
>
> I bypassed this problem by having my unit tests to use a system 
> environment variable that both Wrapper and Java would interpret as 
> being the same.
>
> Marco
>
> ----- Original Message ----- From: "Geoffrey Mitchell" 
> <ga...@im...>
> To: <wra...@li...>
> Sent: Thursday, April 13, 2006 6:05 PM
> Subject: Re: [Wrapper-user] Wrapper on CruiseControl doesn't work
>
>
>> I just avoid relative paths, which I generally think is a good idea 
>> anyway. It's good to know that that property is there now, though.  I 
>> will probably make use of it in the future.  In my current 
>> implementation, I have hacked the wrapper script to not change the 
>> working directory, and it works great!
>>
>> Leif Mortenson wrote:
>>
>>> Geoffrey,
>>>
>>>> I know that Cruise and the wrapper both have some expectations 
>>>> regarding your current working directory (something I personally 
>>>> regard as a sin, but that's just my opinion).
>>>
>>> I actually agree with you.  But the problem is that the working 
>>> directory is not consistent
>>> between running as a console app and running as a service under 
>>> windows. When run
>>> as a service, the working directory is always set to the system32 
>>> directory.   This means
>>> that relative paths in an application become pretty much 
>>> impossible.   I always like being
>>> able to write apps that are deployed as a zip or tar file and then 
>>> unpackaged anyplace
>>> and run.   Having a known fixed working directory as a base makes 
>>> everything just work.
>>>