Am 20.01.2012 19:55, schrieb Stefan Pendl:
Am 20.01.2012 10:46, schrieb lad...@web.de:
Hello Malte,
i don't remember where i read it, but someone complained that setting an
environment variable in the wpkg client for the wpkg logfile path
doesn't work as it's not expanded. That's why i have to use hard codes
paths.
Anyway, according to the wpkg documentation, that i posted, it should
also be possible to override a environment variables inside wpkg. But
yes, this is not what i am looking for.
I talk about the path to the logfile that i have to set in the
settingsfile which can be used to import the settings or automatically
install the wpkg client.
Quote from config.xml:
****************************************************************************
* Path where the logfiles are written to. This might be an UNC path on
the
* network as well as a local path. Environment variables are expanded.
*
* Examples:
* <param name='log_file_path' value='%TEMP%' />
* <param name='log_file_path' value='\\\\server\\share\\dir' />
*
* Default value : "%TEMP%"
* Command-line switch: /log_file_path:<path>
****************************************************************************
So you can use environment variables to specify the log file path.
I would leave the WPKG client settings as generic as possible.
--
Stefan P.
Hello Stefan,
thank you for your reply. Unfortunatelly i don't talk about this
logfile, but about the logfile which is written by the
wpkg-client-service according to its own status.
Here is a screenshot where you can set the path:
http://img803.imageshack.us/img803/1950/wpkglogfilepath.png
and the logfile contains something like that:
############
2012-01-04 15:04:56 -> Initializing socket...
2012-01-04 15:04:56 -> ServiceStart->SERVICE_RUNNING
2012-01-04 15:05:06 -> System query service status
...
2012-01-12 03:20:34 -> System query service status
2012-01-12 03:23:06 -> Before create shared memory: successfuly done.
2012-01-12 03:23:06 -> Create shared memory: successfuly done.
2012-01-12 03:23:06 -> Set script security context: successfuly done.
2012-01-12 03:23:06 -> Network resource required
2012-01-12 03:23:06 -> Network resource: successfuly connected
2012-01-12 03:23:06 -> Starting script action execution
2012-01-12 03:27:20 -> Script action execution done.
2012-01-12 03:27:20 -> Script execution: successfuly done
2012-01-12 03:27:20 -> Network resource: successfuly disconnected
2012-01-12 03:27:21 -> System send shutdown signal
2012-01-12 03:27:24 -> WPKG Service: successfuly done
2012-01-12 03:27:24 -> Working done. Perform cleanup.
2012-01-12 03:27:26 -> Cleanup done.
############
Regards Ronny
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
