02-18-2013
Under VM, not dirty pages stay mapped in case anyone wants to read them through a mmap(). If you need a page, they can be taken, but they are not free. You can run a job that mmap()'s a file, read the whole file into ram, exit, run it again, and when it mmap()s the file again, the old pages are mapped into the new process memory range and it runs much faster. This is what happens with libc.so: everyone runs printf() from the same ram page.
8 More Discussions You Might Find Interesting
1. Linux
New to the forum.
I am running CentOS release 5.3 (Final) and have run into a unique situation.
I have been able to determine that we have a swap memory leak due to an issue with an asterisk server. This specific issue takes approximately 2-3 months for enough of the swap to to be used before... (1 Reply)
Discussion started by: g0neinsane
1 Replies
2. Red Hat
hi
i've notice a huge problem on my newly installed centOS server and i have no idea how to solve it and where to start..
memory on server 3 GB and it goes down, down, down..
after reboot it shows 71mb used
after a hour its 76mb
and after 24h it's around 200
later = more
i have NO idea... (7 Replies)
Discussion started by: tip78
7 Replies
3. Red Hat
HI All,
I am trying to setup DNS on my centOS server.
I am using bind software to setup DNS.
The following errors have getting.
==================================================
Error in named configuration:
zone localdomain/IN: loaded serial 42
zone localhost/IN: loaded serial 42... (4 Replies)
Discussion started by: phpconnect
4 Replies
4. Red Hat
I have compiled a new kernel (3.2.9) for centos 4/5/6 servers. There is an issue with the centos 4, 32 bit servers. The kernel changes the order in which the MAC address is determined and because of this the server network does not come up as the wrong MAC address are assigned. Even if we specify... (6 Replies)
Discussion started by: anil510
6 Replies
5. UNIX for Advanced & Expert Users
Hi,
We are configuring Freeipa for our LDAP system.
Things seem to work okay when we try and log in with our domain accounts on the LDAP server. But when we try to loggon to the slave it closes the connection.
There is an option in authconfig-tui to configure IPA. However, the senior admin... (0 Replies)
Discussion started by: mojoman
0 Replies
6. Filesystems, Disks and Memory
Hi,
i have just installed 4 gb RAM ddr3 on OS Windows 7 32 bit.
In "manage peripherals" i see this section:
Memory installed (ram) : 4,00 gb (2,30gb usable)
Why only 2,30 gb usable ?
In Windows 7 32bit the maximum size is not 3,00gb ?
see file attached, please (4 Replies)
Discussion started by: nash83
4 Replies
7. UNIX for Advanced & Expert Users
Hi,
Which tools or method is popular, simple and effective, to check memory such as bad sector, throughput and performance?
Thank you.
- j (5 Replies)
Discussion started by: hce
5 Replies
8. AIX
Hi,
Can anyone explain this please.....
A simple test program...
### snip
#include <stdio.h>
main() {
static int n;
n = 6;
printf("hello %d\n", n);
n=7;
}
### snip
64 bit compile/link.... (2 Replies)
Discussion started by: bagpussnz
2 Replies
LEARN ABOUT OPENSOLARIS
lx
lx(5) Standards, Environments, and Macros lx(5)
NAME
lx - Linux branded zone
DESCRIPTION
The lx brand uses the branded zones framework described in brands(5) to enable Linux binary applications to run unmodified on a machine
with a Solaris Operating System kernel.
The lx brand includes the tools necessary to install a CentOS 3.x or Red Hat Enterprise Linux 3.x distribution inside a non-global zone.
The brand supports the execution of 32-bit Linux applications on x86/x64 machines running the Solaris system in either 32-bit or 64-bit
mode.
Supported Linux Distributions
The lx brand emulates the system call interfaces provided by the Linux 2.4.21 kernel, as modified by Red Hat in the RHEL 3.x distributions.
This kernel provides the system call interfaces consumed by the glibc version 2.3.2 released by Red Hat.
In addition, the lx brand partially emulates the Linux /dev and /proc interfaces.
Configuration and Administration
The lx brand supports the whole root non-global zone model. All of the required linux packages are installed into the private file systems
of the zone.
The zonecfg(1M) utility is used to configure an lx branded zone. Once a branded zone has been installed, that zone's brand cannot be
changed or removed. The zoneadm(1M) utility is used to report the zone's brand type and administer the zone. The zlogin(1) utility is used
to log in to the zone.
Application Support
The lx zone only supports user-level Linux applications. You cannot use Linux device drivers, Linux kernel modules, or Linux file systems
from inside an lx zone.
You cannot add any non-standard Solaris devices to a Linux zone. Any attempt to do so will result in a zone that zonecfg(1M) will refuse to
verify.
You cannot run Solaris applications inside an lx zone. Solaris debugging tools such as DTrace (see dtrace(1M)) and mdb (see mdb(1)) can be
applied to Linux processes executing inside the zone, but the tools themselves must be running in the global zone. Any core files generated
are produced in the Solaris format, and such files can only be debugged with Solaris tools.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWlxr, SUNWlxu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), zoneadm(1M), zonecfg(1M), brands(5), zones(5), lx_systrace(7D)
SunOS 5.11 19 Sep 2006 lx(5)