Hi. On Wed, Mar 06, 2002 at 04:50:44PM +0100, Cornelis J. de Brabander wrote:
Did anybody succeed in activating that STUPID_LOG_FILE when running zope as a win nt service? Creating a environment variable does not help. I can understand that because this would result in a conflict when running two versions of zope on the same machine. So there would have to be a environment variable that is bound to a specific service.
zope 2.4.3. python 2.1.
Hmm. Don't have that much NT experience, but am doing a zope install currently, may it be possible that you can pass this in the z2.py parameter? You service normally resides in the following registry-key: HKEY_LOCAL_MACHINE\System\Current Control Set\Services\<Your Zope Name>\Parameters\run ("run" may be wrong ... don't know it from the top of my head currently) there is the z2.py call, did you try to append STUPID_LOG_FILE='var\myLogFile.log' or something like that? This would be equivalent to the linux variant of setting it "on-the-fly". Greetings Christian -- Christian Theune - ct@gocept.com gocept gmbh & co.kg - schalaunische strasse 6 - 06366 koethen/anhalt tel.+49 3496 3099112 - fax.+49 3496 3099118 mob. - 0178 48 33 981 reduce(lambda x,y:x+y,[chr(ord(x)^42) for x in 'zS^BED\nX_FOY\x0b'])