|
From: Leif M. <le...@ta...> - 2006-09-25 14:10:05
|
Hans, Can you describe your directory structure a bit more. Where is the wrapper.log file that you are seeing being generated? I ask because the Wrapper has a fail mode where it will default to creating a file called wrapper.log in the same directory as the wrapper.exe if it can not write to the configured wrapper.logfile for any reason. When running as a service, it may also fall back to writing in the windows/system32 directory. Now, as to why it would be unable to write the file. The Wrapper runs as the currently logged in user when running console mode. When it is running as a service however, it will default to running as the SYSTEM user. You can change this using the wrapper.ntservice.account property, but the default is the SYSTEM user. If you have set up any access permissions on your directory structure, it may not be possible for the SYSTEM user to write to the directory you have specified for your log file. The SYSTEM user is also unable to access network drives. Cheers, Leif Hans Jenséus wrote: > On Win XP, when I start my app (using WrapperSimpleApp) with wrapper.exe -c config.conf > System.out shows up in the logfile that is specified in config.conf > > But if I start my app as an NT service (using wrapper.exe -t config.conf) > then System.out shows up in wrapper.log > > The logging & NT part of config.conf looks like: > wrapper.logfile = ../JavaServiceWrapper/logs/DataServer-YYYYMMDD.log > wrapper.logfile.format = LPTM > wrapper.logfile.maxfiles = 7 > wrapper.logfile.rollmode = DATE > wrapper.syslog.loglevel = NONE > > wrapper.ntservice.description = The DataServer > wrapper.ntservice.displayname = DataServer > wrapper.ntservice.name = DataServer > wrapper.ntservice.interactive = false > wrapper.ntservice.starttype = AUTO_START > > I would like to have System.out to go into the logfile when I run as a service (to get rolling going) > Is there a property that I've missed or what should I do? > > R. > > Hans > |