ANNOUNCEMENT: NSD 1.3.0 alpha 1

Miek Gieben miekg at
Mon Sep 22 17:55:09 UTC 2003

[On 22 Sep, @19:00, Michael wrote in "Re: ANNOUNCEMENT: NSD 1.3.0 al ..."]
> >>>>> "Erik" == Erik Rozendaal <erik at> writes:
>     Erik> When NSD starts it loads the database into memory.  After doing so,
>     Erik> it forks of a (configurable) number of child servers to handle UDP
>     Erik> and TCP connections.  By default there is a single TCP server and a
>     Erik> single UDP server.  The child servers do not modify the database,
>     Erik> so the operating system can share the memory pages between the
>     Erik> parent process and the child process.  Unfortunately, systems that
>     Erik> do not allow memory overcommit will reserve memory anyway.
>   Okay, got that.
>   But, a *Linux* system in default overcommit mode might kill NSD off
> randomly. (or other processes) Solaris does different things.

if you mean the OOM killer, upgrade to linux 2.4.23-pre5. A previous prepatch
removed the OOM killer from the stable linux tree.

    grtz  Miek

In theory, there is no difference between theory and practice.
In practice, there is.

More information about the nsd-users mailing list