ANNOUNCEMENT: NSD 1.3.0 alpha 1
mcr at sandelman.ottawa.on.ca
Mon Sep 22 17:00:07 UTC 2003
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Erik" == Erik Rozendaal <erik at nlnetlabs.nl> 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 the data can, and should be shared (read-only), then the *correct* thing
is to mmap() things appropriately. That is the right thing to do, even on a
system that supports overcommit.
] Out and about in Ottawa. hmmm... beer. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian/notebook using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat
-----END PGP SIGNATURE-----
More information about the nsd-users