Hi,
I have a custom logger in a package registered with utility
In the code it sets itself a logfile to write to, up to now that has
been in a 'log' directory in the package itself.
Now I want to use a log file which is in the buildout of the
application. How could I go about finding that dire
Hello zopers,
well this is my third try to ask a question, after the first two ones
went totally ignored, in the last few days. The second one was quite
simple: how do I instruct the ftp server to write some lines in the
access log ?
Silence. How comes ? Did I hurt or piss off anyone ? If so
On Friday 23 November 2007, catonano wrote:
> Hello zopers,
>
> well this is my third try to ask a question, after the first two ones
> went totally ignored, in the last few days. The second one was quite
> simple: how do I instruct the ftp server to write some lines in the
> access log ?
I think
Hi Catonano
> Betreff: [Zope3-Users] third try: containment
>
> Hello zopers,
>
> well this is my third try to ask a question, after the first
> two ones went totally ignored, in the last few days. The
> second one was quite
> simple: how do I instruct the ftp server to write some lines
> in
Hi Jürgen,
Thanks! I'll try that out.
Darryl
On Fri, 2007-11-23 at 11:00 +0100, Jürgen Kartnaller wrote:
> In your buildout you do :
>
> [instance]
> recipe = zc.zope3recipes:instance
> application = app
> address = 8080
> zope.conf =
>
>
> storagedir ${buildout:directory}/parts/log
>
In your buildout you do :
[instance]
recipe = zc.zope3recipes:instance
application = app
address = 8080
zope.conf =
storagedir ${buildout:directory}/parts/log
If you need the log dir precreated you do :
[extfiledir]
recipe = lovely.recipe:mkdir
path = parts/log
To access the prod
Thierry Florac wrote:
As it's name implies, RAMCache utility only stores it's data in RAM. So
I guess that ZODB won't be impacted by cache updates, as other Zope
frontends...
So what do you mean by "find it's way back to ZEO" ? And how can you
handle this ??
Oh, I have no idea about RAMCache...
