On my laptop, the primary consumer of mapped device memory is, unsurprisingly, the video card, which consumes 256MB in the range E0000000-efffffff: Other miscellaneous devices account for most of the rest, and the PCI bus reserves additional ranges for devices as part of the conservative.
The configuration is the same as for Windows but with the following changes: The Linux server does not have to be part of the Windows domain.
There are four components to the configuration of the built-in Tomcat support for Windows authentication.
From the testing to date it is known that: The host name used to access the Tomcat server must match the host name in the SPN exactly else authentication will fail.The Memory Manager of course tries to make the most of that memory by using it as a file cache (the standby list as well as for zeroed memory (the zero page list and Vista's Superfetch feature prefetches data and code into the standby list.Configuration of a Windows server as a domain controller is outside the scope of this how-to.Local kdc.local:88 domain_realm dev.Originally, there was no need to even consider support for more than 4GB on clients because that amount of memory was rare, even on servers.Built-in Tomcat support, kerberos (the basis for integrated Windows authentication) requires careful configuration.
980MB therefore consumes almost half the available 2GB of system virtual address space, leaving only 1GB for mapping the kernel, device drivers, system cache and other system data structures, making that a reasonable cut off: That's also why the memory limits table lists lower limits.
Pushing the Limits of Windows: Processes and Threads.The LoginModule used is a JVM specific one so ensure that the LoginModule specified matches the JVM being used.The spnego authenticator will work with any Realm but if used with the jndi Realm, by default the jndi Realm will use the user's delegated credentials to connect to the Active Directory.Apache httpd Apache httpd does not support Windows authentication out of the box but there are a number of third-party modules that can be used.The name of the login configuration must match the value used by the authentication valve.Here's the output of Meminfo when I run it on that system with the -r switch to dump physical memory ranges: Note the gap in the memory address range from page 9F0000 to page 100000, and another gap from DFE6D000 to ffffffff (4GB).