kde memory management


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users kde memory management
# 1  
Old 11-29-2009
kde memory management

Hi everyone!

I am running KDE 3.5 on a Slackware 12.1 with 1.5Gb of RAM and have the following question:

Running ps on regular intervals of 1 min, I see that 1.3Gb of RAM are being used, leaving me with 0.2Gb of free memory. I tried locating the most greedy app running, which was Kontact and after stopping it nothing changed. Any ideas of what might be going on?

Thanks in advance
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Efficient UNIX Memory management for Running MapReduce Jobs.

We are trying to set up a single node cloudera hadoop cluster having 16 GB as RAM on linux machine. We are setting up 5.4.2 version. Now when we check statistics post the installation and run the top command we find that only 1 -2 GB is available. when we trigger map reduce sample job - no... (2 Replies)
Discussion started by: ketankirange
2 Replies

2. Solaris

Solaris 10 - memory management confusion

Hello i have a Problem - my Server is running with following MEM Information (from TOP): Memory: 32G phys mem, 4195M free mem, 10G total swap, 9788M free swap So i think - no problem, 4GB Free, not swapin. So - our programmer wants to know what process taking how much memory - i... (5 Replies)
Discussion started by: roorbacj
5 Replies

3. Shell Programming and Scripting

Memory management

Hello all. I have a script that uses two arrays in the beginning. Saves certain values that i am extracting from df -h command. array1 and array2 where i is from 0 to 9. It then goes on and saves the values of the arrays into variables. for i 0 to 9 , tmp= array2 // I am no writing the... (4 Replies)
Discussion started by: Junaid Subhani
4 Replies

4. Solaris

Memory management in zones

whats the difference between setting zone capped-memory from zoncfg and setting rctl: name: zone.max-locked-memory .. if changed the zone.max-locked-memory with prctl it does not change in rcapstat .. but if change with rcapadm it reflects in rcapstat o/p (0 Replies)
Discussion started by: fugitive
0 Replies

5. UNIX for Advanced & Expert Users

virtual memory management, swapping paging

can anybody explain me the concepts virtual memory mangement, swapping and paging? although i roughly know what they are , i need more solid distinction between them, and also i want to figure out the relations between them? do you have any well-defined definitons for this concepts? (2 Replies)
Discussion started by: gfhgfnhhn
2 Replies

6. Programming

Programming for Memory Management

Hi I am relatively new to programming on UNIX platform. I was wondering if there is any system call so that a process can access systems page table or swap pages from main memory by specifying the page number. I am trying to implement various page replacement algorithms like LRU, OPT, FIFO etc.... (1 Reply)
Discussion started by: jayesch
1 Replies

7. UNIX for Advanced & Expert Users

unix memory management

i am looking for the books or web-sites which explains the unix memory management in detail. do you know any useful material? (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies
Login or Register to Ask a Question
KDEINIT4(8)							 KDE User's Manual						       KDEINIT4(8)

NAME
kdeinit4 - Start all other KDE programs and kdeinit loadable modules (KLMs). SYNOPSIS
kdeinit4 [--help] [--no-fork | --no-kded | --suicide] [+programs | programs] DESCRIPTION
kdeinit4 is a process launcher somewhat similar to the famous init used for booting UNIX. It executes KDE programs and kdeinit loadable modules (KLMs) starting them more efficiently. Using kdeinit4 to launch KDE applications makes starting a typical KDE application a couple times faster and reduces memory consumption by a substantial amount. kdeinit4 is linked against all libraries a standard KDE application needs. With this technique, starting an application becomes much faster because now only the application itself needs to be linked whereas otherwise both the application as well as all the libaries it uses need to be linked. DISADVANTAGES
The process name of applications started via kdeinit4 is "kdeinit4". This problem can be corrected to a degree by changing the application name as shown by ps. However, applications like killall will only see kdeinit4 as the process name. To workaround this, use kdekillall (from kdesdk/scripts) for applications started via kdeinit4. OPTIONS
--help Show help about options --no-fork Do not fork, i.e. do not exit until all the executed programs ends --no-kded Do not start kded --suicide Terminate when no KDE applications are left running +programs runs the programs handling requests programs runs the programs without handling requests USAGE
A standard way to run this program is by simply specifying the following command at the prompt kdeinit4 program or kdeinit4 +program FILES
/tmp/kde-$USER/kdeinit4_$INSTANCE ... ENVIRONMENT VARIABLES
$HOME Specifies the home directory of the current user $KDE_HOME_READONLY Specifies if the home directory of the current user is read only $KDE_IS_PRELINKED If set, tells kdeinit4 that the KDE programs are pre-linked. (Prelinking is a process that allows you to speed up the process of dynamic linking.) $KDE_DISPLAY If set, tells kdeinit4 that it is running on a KDE desktop. SEE ALSO
kded, kdekillall BUGS
There are probably tons of bugs. Use bugs.kde.org: http://bugs.kde.org to report them. AUTHORS
Waldo Bastian <bastian@kde.org>, Mario Weilguni <mweilguni@sime.com>, Lubos Lunak <l.lunak@kde.org>. 2008-10-03 KDEINIT4(8)