6.8. Locking ntpd in memory

Currently, ntpd will lock itself in memory if the appropriate system calls are available.

For some OSes, the amount of locked memory is currently hardcoded in ntpd.c.

This is Suboptimal.

• AIX: reserve 32k of extra stack space (less 8 4k pages).
• WINNT callls SetProcessWorkingSetSize() and VirtualLock(), at about 4MB(?).
• Systems that use setrlimit() and mlockall() seem to reserve an extra 50 4k pages.
  • this seems to be too much for some *BSD systems, and not enough for some linux systems.

Related Topics: NtpdProcessResidencyIssues, Bug #387