On Fri, 12 Nov 2004, Jure [ISO-8859-2] Pe_ar wrote:
On Fri, 12 Nov 2004 13:12:10 -0500 (EST)
Igor Brezac <[EMAIL PROTECTED]> wrote:
Use lsof.
Maybe my question wasnt clear enough. When fuser somefile shows ~20
processess, how do I figure out which one is the first that caused all
others to block? O
On Fri, 12 Nov 2004 13:12:10 -0500 (EST)
Igor Brezac <[EMAIL PROTECTED]> wrote:
> Use lsof.
Maybe my question wasnt clear enough. When fuser somefile shows ~20
processess, how do I figure out which one is the first that caused all
others to block? Or first two that are fighting for a lock?
> Thi
On Fri, 12 Nov 2004, Jure [ISO-8859-2] Pe_ar wrote:
On Thu, 11 Nov 2004 08:49:38 -0500
Ken Murchison <[EMAIL PROTECTED]> wrote:
Try an strace/truss on the process and see what its doing.
I did a strace on reconstruct to determine on which file it was locking and
determined it's cyrus.header. Looki
On Thu, 11 Nov 2004 08:49:38 -0500
Ken Murchison <[EMAIL PROTECTED]> wrote:
> Try an strace/truss on the process and see what its doing.
I did a strace on reconstruct to determine on which file it was locking and
determined it's cyrus.header. Looking at the locking order in wiki I see the
cyrus.h
Jure Pe_ar wrote:
On Wed, 10 Nov 2004 16:17:18 +0100
Jure Pe_ar <[EMAIL PROTECTED]> wrote:
Is this problem on just user/sta* mailboxes a coincidence? Or can it point
to something with one of the databases?
I'm seeing this again, in the morning it was agains user/ab* mailboxes, now
it's user/iz*.
On Wed, 10 Nov 2004 16:17:18 +0100
Jure Pe_ar <[EMAIL PROTECTED]> wrote:
> Is this problem on just user/sta* mailboxes a coincidence? Or can it point
> to something with one of the databases?
I'm seeing this again, in the morning it was agains user/ab* mailboxes, now
it's user/iz*.
This never ha
