Hello,
I would like to confirm that ZConfig keys are case insensitive and
that the corresponding attributes on the config object returned by the
'loadConfig' call are always lower case.
The only thing that seems relevant about keys and case sensitivity in
the documentation does not state it
Hi all,
I am starting to venture into the wonderful world of Zope! With the
benefit of a complete lack of Zope experience, I have been able to look at
the Windows service support from a fairly clean slate. However, I also
realize this lack of experience means my ideas may be naive - hence I
On Tue, 2004-08-03 at 03:34, Gerhard Schmidt wrote:
Hi,
we have some problems with our tempstorage on out ZEO client.
We are running 6 zope Frontend server and one ZEO server. Serving
Both main and temp storage.
I runs well for some days. But than it stops working an reports the
On Wed, Aug 04, 2004 at 08:37:28AM -0400, Chris McDonough wrote:
Wow! You appear to be the first person to get this symptom who does not
use Plone. This is a great data point. This error is being tracked at
http://zope.org/Collectors/Zope/1401 . There is no solution currently,
we need
On Wed, 2004-08-04 at 07:35, Mark Hammond wrote:
Hi all,
I am starting to venture into the wonderful world of Zope! With the
benefit of a complete lack of Zope experience, I have been able to look at
the Windows service support from a fairly clean slate. However, I also
realize this lack
On Wed, 2004-08-04 at 08:47, Gerhard Schmidt wrote:
On Wed, Aug 04, 2004 at 08:37:28AM -0400, Chris McDonough wrote:
Wow! You appear to be the first person to get this symptom who does not
use Plone. This is a great data point. This error is being tracked at
On Wed, 04 Aug 2004 10:24:30 +0200, Godefroid Chapelle
[EMAIL PROTECTED] wrote:
I would like to confirm that ZConfig keys are case insensitive and
that the corresponding attributes on the config object returned by the
'loadConfig' call are always lower case.
It sounds like I need to clarify
Mark Hammond wrote:
...
I propose:
We insist the child process can be created and continues to run for x
seconds (where x~5).
I recommend against this strategy. It's too implicit and has bitten us on
Unix in the past. The problem with the strategy if the program starts very fast
and then dies,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
~ The whole problem might be related to some version of
| PlacelessTranslationService.
| Christian Heimes' hint was to upgrade to the latest PTS version from the
| CVS which
| seems to solve the problem although the traceback
Gerhard Schmidt wrote at 2004-8-3 09:34 +0200:
...
Module Products.Sessions.SessionDataManager, line 94, in getSessionData
Module Products.Sessions.SessionDataManager, line 183, in _getSessionDataObject
SystemError: error return without exception set
I had an issue in the same line:
it
On Wed, 2004-08-04 at 17:42, Dieter Maurer wrote:
Gerhard Schmidt wrote at 2004-8-3 09:34 +0200:
...
Module Products.Sessions.SessionDataManager, line 94, in getSessionData
Module Products.Sessions.SessionDataManager, line 183, in _getSessionDataObject
SystemError: error return without
[Me]
I propose:
We insist the child process can be created and continues to
run for x seconds (where x~5).
[Jim]
I recommend against this strategy. It's too implicit and has
bitten us on
Unix in the past. The problem with the strategy if the
program starts very fast
and then dies, we
I propose:
Each time the child process terminates with a non-zero
return code, the tail
x-bytes of the child output be written to the Windows event
log, where x~2k.
This is a good idea. FWIW, I believe the Zope HEAD already has some
work done towards this (in
On Wed, 2004-08-04 at 19:56, Mark Hammond wrote:
On Windows however, runzope is executed as a *child* of the service. If
the child fatally fails, the service itself is still reporting success, and
hopelessly attempting a restart. The service needs to know if the child
fatally failed. This
On Wed, 2004-08-04 at 20:24, Mark Hammond wrote:
This is a good idea. FWIW, I believe the Zope HEAD already has some
work done towards this (in
lib/python/nt_svcutils/service.py), although
the child output goes to a logfile instead of the event log. It would
be nice to make the output
FWIW, the equivalent of the service manager code under UNIX
is zopectl
rather than runzope.
Ahh, ok. That makes more sense now, thanks.
When you say these errors above, do you mean any unhandled
exception?
If so (and any nonzero exit code indicated a startup
failure), would we
really
16 matches
Mail list logo
