Sponsored Content
Operating Systems Linux Memory issue on My CentOS 5.8 x64 bit server Post 302770810 by radoulov on Monday 18th of February 2013 12:13:42 PM
Old 02-18-2013
Because the Linux kernel works that way, the cached memory is used to optimize access to slow access data, usually disks.
Most of that could be considered available ("free") memory.

Last edited by radoulov; 02-18-2013 at 01:21 PM..
 

8 More Discussions You Might Find Interesting

1. Linux

Memory issues iin CentOS release 5.3 (Final)

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

centOS memory leak - MEGABYTES per day

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

Domain name server installation issue in centOS

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

Centos 4 32 bit - New kernel ethX MAC address order issue

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

Freeipa issue on Centos 6.3

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

Maximum Memory RAM for windows 7 32 bit

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

Which memory test tool is popular on CentOS 6?

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

Gdb on a 64 bit executable - cannot access memory

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
mem(7D) 							      Devices								   mem(7D)

NAME
mem, kmem, allkmem - physical or virtual memory access SYNOPSIS
/dev/mem /dev/kmem /dev/allkmem DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer. The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an I/O device. The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory that is associated with an I/O device. You can use any of these devices to examine and modify the system. Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information. The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2). ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a non-existent or unimplemented location (mem, kmem, allkmem). EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem spe- cial file. ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address. FILES
/dev/mem Provides access to the computer's physical memory. /dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an I/O device. /dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an I/O device. SEE ALSO
llseek(2), mmap(2), read(2), write(2) WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is changed. SunOS 5.10 18 Feb 2002 mem(7D)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy