|
From: Leif M. <le...@ta...> - 2006-07-30 01:11:02
|
Mark, The Java Service Wrapper, like all applciations, will be run as the current user when run as a console app, or a standalone application. When run as a service, they will be run as the SYSTEM account. I think this is what you are seeing. If you look at the task manger while the service is running, you will see that both the wrapper.exe and java.exe processes are running as SYSTEM. You can control this by using the wrapper.ntservice.account and password properties to run as a specific account. Also note that the SYSTEM user will not have access to network drives, but that non-SYSTEM users will not be able to interact with the desktop. Cheers, Leif Mark Modrall wrote: > > Hi… > > I noticed something a little odd while running Cruise Control under > JSW. All the files updated by svn and the log files have an odd owner. > When I was first trying to get it working, I found that running as a > service, JSW could write neither its nor CC’s log files unless I > changed the service definition to run under a specific account. > > The account I chose was a domain account (not local) with local > membership in the Administrators group. When running CC from a login, > all log files and svn updates are owned by the login account. When > running as a service, all log files and svn updated-files show up as > being owned by the local Administrator group (no specific owner). > > Anyone seen this before? > > Thanks > > -Mark > |