similar to: [PATCH] support SO_REUSEPORT on new listeners (:reuseport)

Hi, I am getting failing tests on both OSX and debian squeeze, but the errors are different. On both my machines, it is commit 7c125886b5862bf20711bae22e6697ad46141434 that breaks the tests. I am using an old(ish) version of ruby: 1.9.3p125, but I don''t think that should matter. The error I get when I test 4.7.0 on OSX 10.7.5: : Finished tests in 0.041678s, 263.9282 tests/s,

On Sat, 28 Dec 2019 17:02:09 +0100 richard lucassen via nsd-users <nsd-users at lists.nlnetlabs.nl> wrote: > The problem is (was) that I used "include:" statements in nsd.conf > to load zone information. Apparently nsd does not reread the include > files upon a SIGHUP. I scripted everything into 1 file and a HUP > rereads the zone info now. Wrong, I made a mistake it

IPv4 addresses started looking very ugly the first time I got IPv6 working on bogomips.org. In case somebody else can''t stand how IPv4-mapped-IPv6 addresses look, the workaround is to use two listeners and ensure the IPv6 one is ipv6only. Unicorn itself supports IPv6, too, but nobody uses/needs it. I''ll add :ipv6only support shortly (probably tomorrow). >From

Hello, can someone explain these errors Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: Transfer started. Oct 27 15:34:06 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27

Hello all, Tested on linux 2.6.18 (Centos5) and FreeBSD 7.0. You would execute it like below (which basically makes tftp reply back with same port is listening on ) tftpd --port-range 69:69 -4 -s /tftpboot/ --- tftp-hpa-0.49/tftpd/tftpd.c 2008-10-21 01:08:31.000000000 +0300 +++ tftp-hpa-0.49-tftpd-reuseport.c 2010-03-03 15:19:26.000000000 +0200 @@ -524,6 +524,11 @@ #ifndef __CYGWIN__

I just read about Linux v3.9's SO_REUSEPORT feature and decided to implement it for Dovecot. Would be interesting to know how it works for people :) It's going to be in v2.2.6, which I'm planning on releasing tomorrow. Note especially the warning about the bug: http://hg.dovecot.org/dovecot-2.2/rev/a991a0547daa So the idea is that you'd do something like: service imap-login {

On Mon, May 15, 2017 09:53, wwp wrote: > On Mon, 15 May 2017 09:22:54 +0200 "Walter H." > <walter.h at mathemainzel.info> wrote: > >> On Sun, May 14, 2017 11:00, wwp wrote: >> > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." >> > <Walter.H at mathemainzel.info> wrote: >> > >> > This might become off-topic with my

On 24 Apr 2017, at 15.41, Timo Sirainen <tss at iki.fi> wrote: > > On 24 Apr 2017, at 4.04, Christian Balzer <chibi at gol.com <mailto:chibi at gol.com>> wrote: >> >> >> Hello, >> >> Just to follow up on this, we've hit over 16k (default client limit here) >> hibernated sessions: >> --- >> dovecot 119157 0.1 0.0

Klaas Jan Wierenga wrote: > Hi Henri and others, > > Very interesting post about TCP_CORK. I would be very interested in having > it applied in the next version of Icecast. I'd be more interested in some figures to show there being a benefit, most examples talk about HTTP servers with short lived connections where sendfile(2) is used. > For low-bitrate streams the problem

Hi there, I''ve got a Rails app that''s a little unusual in that it maintains a database representation of a filesystem (for an image gallery). Thus, if the filesystem is essentially ''out of date'' then the controller''s list action will end up invoking a model update (which involves a filesystem scan). I''m using sqlite3 as this app will be

Klaas Jan Wierenga wrote: >>This is exactly why it was implemented, a few people complained about >>the overhead with large numbers of listeners, not only because of the >>TCP overhead but also the fact that it reduces the write syscall >>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable >>benefits wrt icecast? It might prove helpful if available but

Hello, Just to follow up on this, we've hit over 16k (default client limit here) hibernated sessions: --- dovecot 119157 0.1 0.0 63404 56140 ? S Apr01 62:05 dovecot/imap-hibernate [11291 connections] dovecot 877825 0.2 0.0 28512 21224 ? S Apr23 1:34 dovecot/imap-hibernate [5420 connections] --- No issues other than the minor bug I reported, CPU usage is

Hi Stephen, Many thanks for your answer. Unbound under OpenBSD is compiled with few options: Version 1.9.4 Configure line: --enable-allsymbols --with-ssl=/usr --with-libevent=/usr --with-libexpat=/usr --without-pythonmodule --with-chroot-dir=/var/unbound --with-pidfile= --with-rootkey-file=/var/unbound/db/root.key --with-conf-file=/var/unbound/etc/unbound.conf --with-username=_unbound

Hello Walter, On Mon, 15 May 2017 09:22:54 +0200 "Walter H." <walter.h at mathemainzel.info> wrote: > On Sun, May 14, 2017 11:00, wwp wrote: > > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > > <Walter.H at mathemainzel.info> wrote: > > > >> On 13.05.2017 00:29, Robert Moskowitz wrote: > >> > I have been working,

On 24 Apr 2017, at 4.04, Christian Balzer <chibi at gol.com> wrote: > > > Hello, > > Just to follow up on this, we've hit over 16k (default client limit here) > hibernated sessions: > --- > dovecot 119157 0.1 0.0 63404 56140 ? S Apr01 62:05 dovecot/imap-hibernate [11291 connections] > dovecot 877825 0.2 0.0 28512 21224 ? S

We now give an example of how a before_fork hook can be used to incrementally migrate off the old code base without hitting a thundering herd (especially in the "preload_app false") case. Also comment on the per-worker listen usage in the RDoc, not just a hidden comment. --- I just pushed this out earlier, this example was inspired by Chris Wanstrath''s before_fork hook but

> This is exactly why it was implemented, a few people complained about > the overhead with large numbers of listeners, not only because of the > TCP overhead but also the fact that it reduces the write syscall > overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable > benefits wrt icecast? It might prove helpful if available but more info > is needed. As

Hello all, I''d like to have nginx+passenger show the custom (Default) error pages when a HTTP 500 error occurs in my app. I am running a rails 2.3 app on nginx 1.2 with passenger 3.0.7 Here is my nginx config file: #user nobody; worker_processes 16; error_log /opt/nginx/logs/error.log info; pid /opt/nginx/logs/nginx.pid; worker_rlimit_nofile 32768; events {

Hello, in /etc/sysconfig/network-scripts/ifcfg-eth0 I have this <ifcfg-eth0> ... IPV6INIT=yes IPV6ADDR=prefix::5 IPV6ADDR_SECONDARIES="prefix::2 prefix::3 prefix::4" IPV6_AUTOCONF=no IPV6_DEFAULTGW=prefix::1 IPV6_DEFAULTDEV=eth0 </ifcfg-eth0> when I enter ifconfig the IPv6 addresses are in a different order <ifconfig> eth0 Link encap:Ethernet HWaddr ... inet addr:...

On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status