[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: Lingering port binding after killing conserver on Sol8

Bryan Stansell bryan@conserver.com
Wed, 27 Jun 2001 19:01:23 -0700 (PDT)

What version are you running?  If it's 7.0.0 or 7.0.1 it's a bug in the
configure.in file.  The libraries weren't checked before the function
calls and it fails to find setsockopt() on Solaris (and possibly
others).  If you are using 7.0.2 and you have this problem, I'd love to
see the output of ./configure.

Hope that helps shed some light.


On Wed, Jun 27, 2001 at 06:47:12PM -0700, Trevor Fiatal wrote:
> Greetings.
> I'm running conserver on Solaris 8 (SPARC), patchlevel MU4.
> I compiled conserver as a 32-bit binary using gcc 2.95.3.
> Overall, conserver is great.  It fscking rocks.  However,
> it does have one major annoying behaviour in my environment:
> when you kill the conserver daemon, either via in-band kill
> from a 'console' client or via the 'kill' command, it does
> NOT correctly relinquish the TCP port it had been listening
> on.  In my case, it's tcp/782.
> This is really ugly because the port hangs around in TIME_WAIT
> for a long time (>5 minutes on my systems) and I can't restart
> the conserver daemon until the timeout expires.  Clearly, this
> makes restarting conserver something you don't want to do
> unless you *really* have to.  It probably goes without saying,
> but being able to 'kill -HUP' the daemon to cause a reread of
> the config file would be a Very Good Thing.
> Has anyone else seen this behaviour, or is it just me?
> -Trevor
> -- 
> Trevor Fiatal -- trevor@seven.com -- http://www.seven.com/
> Co-Founder
> Seven
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users