search for: getaddrbyname_r

...iteration of 24k all the way up to 128k again. (ie. 24k, 48k, 96k...) If there is more information needed please ask and I will provide. Server_info: Runtime Configuration: Using nanosleep() as sleep method Using 64 chunks of 8192 bytes for client backlog Using linux own gethostbyname_r() and getaddrbyname_r(), which is good. Using posix signal interface to block all sign Thanks, Natr Thomas Kirk wrote: > On Fri, Jul 20, 2001 at 11:13:18AM -0400, AJones! wrote: > >> Where can you get libshout? Ours chokes at roughly 40 users and then >> can't gain access to the admin sections....

...03/Apr/2001:17:59:20] Using nanosleep() as sleep method [03/Apr/2001:17:59:20] Using posix signal interface to block all signals in threads that don't want them [03/Apr/2001:17:59:20] Using 64 chunks of 8192 bytes for client backlog [03/Apr/2001:17:59:20] Using linux own gethostbyname_r() and getaddrbyname_r(), which is good. [03/Apr/2001:17:59:20] System can create max 1024 threads [03/Apr/2001:17:59:20] Starting Admin Console Thread... -> [03/Apr/2001:17:59:20] Starting main connection handler... -> [03/Apr/2001:17:59:20] Listening on host 192.168.1.3... -> [03/Apr/2001:17:59:20] Listening o...

7/20/01 8:49 AM thomas@arkena.com >> What's the trick. My server will hardly serve 4 people without > >Hmm no trick? We dont use ices though we use libshout which is the >liberay that ices use to serv mp3s to icecast. Where can you get libshout? Ours chokes at roughly 40 users and then can't gain access to the admin sections. >> skipping and eventually dropping

...ng nanosleep() as sleep method > [03/Apr/2001:17:59:20] Using posix signal interface to block all signals in > threads that don't want them > [03/Apr/2001:17:59:20] Using 64 chunks of 8192 bytes for client backlog > [03/Apr/2001:17:59:20] Using linux own gethostbyname_r() and > getaddrbyname_r(), which is good. > [03/Apr/2001:17:59:20] System can create max 1024 threads > [03/Apr/2001:17:59:20] Starting Admin Console Thread... > -> [03/Apr/2001:17:59:20] Starting main connection handler... > -> [03/Apr/2001:17:59:20] Listening on host 192.168.1.3... > -> [03/Apr/2...