REFACTOR See LockingNtpdInMemoryDev for discussion of this topic.

6.9. 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_small.png Bug #387

This topic: Support > WebHome > OtherDocumentation > LockingNtpdInMemory
Topic revision: r7 - 2007-05-05 - 16:56:20 - SteveKostecke
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback