Michael Best writes:
 > ... core generation under Solaris ...
I have seen Zope cores under Solaris 2.6.

This means,

  * either the problem you see does not result in a situation
    that usually causes a core dump
  * your configuration prevents cores from being generated.

I expect the latter.

You told us, that you already changed the "ulimit" value.
You know, that there are too values, a soft limit that
can later be changed and a hard limit that can only be
tightened? Maybe, there is some hard limit preventing you
from changing the core size limit or Zope wants to
generate a core that is larger than the size you specified.

You can test core generation independent of Zope
(to clean any configuation problems):

    sleep 500 &
    kill -QUIT %%

This let's "sleep" generate a core.

One you get "sleep" cores, you can hit Zope with the
"-QUIT" signal. Zope's core will be bigger, therefore,
the "ulimit" core limit must be larger.

Once, you can reliably force Zope into a core, you can
look at your instability again.


Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to