Sponsored Content
Operating Systems Linux Memory issue on My CentOS 5.8 x64 bit server Post 302770767 by radoulov on Monday 18th of February 2013 09:03:27 AM
Old 02-18-2013
I don't see any problem with your system: your OS is using less than 1G and all the rest (14G cached) is available for use.
 

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
allegro_exit(3alleg4)						  Allegro manual					     allegro_exit(3alleg4)

NAME
allegro_exit - Closes down the Allegro system. SYNOPSIS
#include <allegro.h> void allegro_exit(); DESCRIPTION
Closes down the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines have been installed. You don't normally need to bother making an explicit call to this function, because allegro_init() installs it as an atexit() routine so it will be called automatically when your program exits. Note that after you call this function, other functions like destroy_bitmap() will most likely crash. This is a problem for C++ global destructors, which usually get called after atexit(), so don't put Allegro calls in them. You can write the destructor code in another method which you can manually call before your program exits, avoiding this problem. SEE ALSO
install_allegro(3alleg4), allegro_init(3alleg4), destroy_bitmap(3alleg4), ex3d(3alleg4), exscn3d(3alleg4), exswitch(3alleg4), exxfade(3alleg4), exzbuf(3alleg4) Allegro version 4.4.2 allegro_exit(3alleg4)
All times are GMT -4. The time now is 03:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy