04-05-2011
use mem= when booting the server (kernel boot line) to change the amount of physical memory seen. That will force swapping sooner.
5 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
they did it...
get it:
http://www.sun.com/software/solaris/get.jsp (0 Replies)
Discussion started by: pressy
0 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. Linux
Hello,
I am using CentOS 5.8 x64 server for our one of internal application which is developed on PHP and Mysql as DB.
Currently there are 8-10 instances deployed on this server some of them are rarely used.
Below is the H/W specification fort the same :-
Procesor :- Intel(R) Xeon(R) CPU ... (6 Replies)
Discussion started by: sunnysthakur
6 Replies
4. Red Hat
I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs:
options {
listen-on port 53 { 127.0.0.1; 10.8.0.19;};
#listen-on-v6 port 53 {... (2 Replies)
Discussion started by: metallica1973
2 Replies
5. 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
MEM(4) Linux Programmer's Manual MEM(4)
NAME
mem, kmem, port - system memory, kernel memory and system ports
DESCRIPTION
mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even
patch) the system.
Byte addresses in mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned.
Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present.
It is typically created by:
mknod -m 660 /dev/mem c 1 1
chown root:kmem /dev/mem
The file kmem is the same as mem, except that the kernel virtual memory rather than physical memory is accessed.
It is typically created by:
mknod -m 640 /dev/kmem c 1 2
chown root:kmem /dev/kmem
port is similar to mem, but the I/O ports are accessed.
It is typically created by:
mknod -m 660 /dev/port c 1 4
chown root:mem /dev/port
FILES
/dev/mem
/dev/kmem
/dev/port
SEE ALSO
chown(1), mknod(1), ioperm(2)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-11-21 MEM(4)