Am Samstag, 27. August 2011, 00:48:20 schrieb bugzilla- daemon at bugzilla.wpkg.org: > MOD: Updated log file handling. Now there is no intermediate local log file > created any more. Instead a log is kept in memory as long as the log > file is not initialized. If anything goes wrong WPKG still tries to flush > the logs at least to a log file in %TEMP%. > This potentially increases efficiency and execution speed slightly. This unfortunately causes a line like this to appear for every run, i.e. whenever a client starts up: 2011-08-30 15:10:48, DEBUG : WPKG 1.2.1-RC10 starting... due to the logLevelDefault of 0xff. We're using [HOSTNAME]-[YYYY][MM][DD][hh] [mm][ss].wpkg.log as logfilePattern, so this causes an unwanted file to be created every time and fills up our reporting tool. If this is intended behaviour, I'll have to work around this. Otherwise, well, maybe the log buffer needs to be an array of some object that includes the entry's level for later filtering. Regards, Malte PS: Is there a way to log to STDOUT instead of a file for debugging? |