Hello,

  Pound does not want to shutdown on freebsd 4.9.
  I installed it using patches from freebsd ports.
  In detail:
     CFLAGS=-DF_CONF=\"$(F_CONF)\"   -O   -pipe   -DAEMON   -D  UNSAFE
     -D_THREAD_SAFE -DNEED_STACK
     LIBS=-lssl -lcrypto

  What happens is. When I try to shutdown pound it quits accepting new
  connections  (it  seems  so),  but  it  does  not  want  to shutdown
  completely.  'top' shows 'soclos' in status. 'netstat' shown several
  connections established.

  What can you suggest?

  P.S.  New pound does not want to start, because it cant bind to port
  80.
[...]

On Tuesday 09 December 2003 18:49, Pavel Merdine wrote:[...]

What does "shut down" mean to you? Is there anything in the logs? More info 
required here...[...]

On Wednesday 10 December 2003 13:34, Pavel Merdine wrote:[...]

So you say Pound does not exit after receiving a signal 15? Try 9 ;-)

It looks like you get stuck zombie-like on some blocking socket I/O. Given 
that this does not happen on any other system (including FreeeBSD in earlier 
versions) it may have something to do with 4.9. Could you try and pinpoint 
the problem?

Secondly, I find it really strange that you would have more than one Pound 
process. The *BSDs implement threads as a user-space library, thus all 
threads run in a single process. Could it be that you started multiple 
instances?

Also: please keep this on the list.[...]

Hello ,

Wednesday, December 10, 2003, 4:43:40 PM, you wrote:
[...]
[...]

I forgot to mention. It cannot be killed even with kill -9 :)
So maybe you're right about FreeBSD.
[...]

The  problem is that this happens only in production environment (when
there  is  lots  of  connections).  I'll try to do something when time
allows.
[...]

The process 375 you see is zombee one. It disappeared after some time.
[...]

Sorry,  I  forgot to tune my mail client for this list to do it for me
:)
[...]