--On Monday, December 09, 2002 4:39 PM + Stephen Grier
<[EMAIL PROTECTED]> wrote:
Henrique de Moraes Holschuh wrote:
There is a more complete solution to the SIGCHILD problems in master,
that fixes all the race conditions that cause the process count to be
lost. I call it the "pid morgue" :-
Henrique de Moraes Holschuh wrote:
> There is a more complete solution to the SIGCHILD problems in master, that
> fixes all the race conditions that cause the process count to be lost. I
> call it the "pid morgue" :-)
>
> It is in the bugzilla, and it is being used in production by the fastmail.f
On Fri, 06 Dec 2002, Oleg Derevenetz wrote:
> Nicola Ranaldo wrote:
> >I think master would check exit value of its childs and decrement the
> >number
> >of ready_workers.
>
> It seems like you perfectly right. I wrote a quick fix (i will be very
> thankful if you check my fix and correct me if
Nicola Ranaldo wrote:
I think master would check exit value of its childs and decrement the number
of ready_workers.
It seems like you perfectly right. I wrote a quick fix (i will be very
thankful if you check my fix and correct me if I am wrong) and it works
:-) Attachment contain this fix.
*
I think master would check exit value of its childs and decrement the number
of ready_workers.
Regards
Nicola Ranaldo
> When some pop3d dies with signal (i.e. SIGTERM), all incoming
> connections to corresponding address:port are hangs. For example, if I
> have pop3d running on 192.168.0.1:
Carson Gaspar wrote:
>
> --On Thursday, December 05, 2002 10:22 PM +0300 Oleg Derevenetz
> <[EMAIL PROTECTED]> wrote:
>
> > When some pop3d dies with signal (i.e. SIGTERM), all incoming connections
> > to corresponding address:port are hangs. For example, if I have pop3d
>
> I can confirm that
--On Thursday, December 05, 2002 4:58 PM -0500 Rob Siemborski
<[EMAIL PROTECTED]> wrote:
This isn't good enough for me to reproduce it.
I have tried both with preforking and without preforking.
I cannot get 2.1.11 to behave like this on Solaris 8.
Master didn't change since 2.1.10 so I don't
On Thu, 5 Dec 2002, Carson Gaspar wrote:
> > When some pop3d dies with signal (i.e. SIGTERM), all incoming
> > connections to corresponding address:port are hangs. For example, if I
> > have pop3d
>
> I can confirm that the same bug exists under Solaris 8 x86 (fully patched)
> with imapd. To repro
--On Thursday, December 05, 2002 10:22 PM +0300 Oleg Derevenetz
<[EMAIL PROTECTED]> wrote:
When some pop3d dies with signal (i.e. SIGTERM), all incoming connections
to corresponding address:port are hangs. For example, if I have pop3d
I can confirm that the same bug exists under Solaris 8 x86
On Thu, 5 Dec 2002, Oleg Derevenetz wrote:
> When some pop3d dies with signal (i.e. SIGTERM), all incoming
> connections to corresponding address:port are hangs. For example, if I
> have pop3d running on 192.168.0.1:110, and issue a command:
>
> $ kill PID_OF_THIS_POP3D
I can't duplicate this. I
I'm seeing some form of crashes as well, but I'm not getting enough
details to really report on them :( When it crashes, I have to kill
everything off including the master, and restart it.
--
Jason Fesler, <[EMAIL PROTECTED]> http://gigo.com/resume.html
"You'll finish first - or not at all" -
Hi all,
I have a problem with cyrus-imapd 2.1.11 working under Solaris 8. Imapd
was built with gcc 2.95.3 and configured with following options:
./configure --with-cyrus-prefix=/usr/local/cyrus
This is a piece of cyrus.conf file:
SERVICES {
imap1 cmd="imapd -C /usr/local/cyrus/etc/1/imapd.co
12 matches
Mail list logo
