Date: Thu, 10 Apr 1997 23:24:53 -0700 (PDT) From: Ian Struble <ian@ian.broken.net> To: dg@root.com Cc: freebsd-hackers@freebsd.org, David Greenman <dg@root.com> Subject: Re: UNIX/LOCAL sockets Message-ID: <XFMail.970411010431.ian@ian.broken.net> In-Reply-To: <199704110351.UAA01733@root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>
> You're a little confused about this. The number of sockets isn't limited
>by SOMAXCONN. The only limit that would affect that is the process open file
>limit. SOMAXCONN limits the number of unaccepted connections that can be
>outstanding in the queue at any given time.
Ah, thanks for clearing that up.
> It sounds like you might need to increase the per-process file descriptor
>limit. That's just a guess, however. The guesses get more accurate with
>information, so if you could perhaps explain what "having some problems" is
This per-process fd limit is exactly what I was thinking about but was just too
tired to put two and two together, let alone find out where to find and change
it. Do I need to add an option to the kernel config file to change this?
Moving right along, let me see what I can do to elaborate on the problem. I am
working on the back-end cgi stuff for a little registration system that is
supposed to be able to handle at least 10 simultaneous registrations at once.
Right now 5 works just fine but 10 causes some problems. I can't really be very
much more specific on the `problems` because someone else's front end is in the
way. Apache is giving me a mysterious little error though :
Title - 500 Server Error
Internal Server Error
The server encountered an internal error or misconfiguration and
was unable to complete your request.
Actually this is the first time I have actually seen the 'Title - 500...' line,
but the rest is the same. Oh, I have been getting these messages with both
Apache ver. 1.1.3 and ver. 1.2b7.
The cgi processes are basically clients that send msgs to one central 'server'
via local sockets which inturn sends all these packets out to a remote site for
processing and then back to the individual CGI's. I know it sounds like alot
of work and could be done straight out of the individual cgi processes, but I
am dealing with people on a firewall who will only allow me a single port send
so I figured this was the only way to go about it.
TIA,
Ian
----
Tussman's Law:
Nothing is as inevitable as a mistake whose time has come.
----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970411010431.ian>