I recently saw that im very short on ram and not really sure why?
Besides top(shown below), is there any possibility to see what process has been using/leaking or whatever has happened?
I have heard that rtorrent has some kind of leak but it hasnt been any problem so far so why would it be that if i havent changed it.

I added 512mb of ram about 2 weeks ago when i noticed that i was low on ram but it didnt really change anything.
top output:

If you want to make top(1) to be usefull for showing memory hog applications, use it like that: top -b -o res

__________________religions, worst damnation of mankind"If 386BSD had been available when I started on Linux, Linux would probably never had happened." Linus TorvaldsLinux is not UNIX! Face it! It is not an insult. It is fact: GNU is a recursive acronym for “GNU's Not UNIX”.vermaden's:linksresourcesdeviantartspreadbsd

This is a common complaint from users, unfortunately it can be difficult explaining that memory is handled quite differently.. rest assured that if you have memory detected by OpenBSD, it won't be wasted.

Multiple "lists" exist in the kernel that track memory usage (..both physical and virtual), one of these is a list of "free" pages.. a page being 4096 bytes memory on most architectures.. memory that is immediately available to processes (..243 megabytes worth on your system).

As previously said, there are multiple lists.. it's more complicated then just "used memory" and "free memory", but the kernel is constantly updating all of these lists while using sophisticated heuristics to make sure the wheels keep turning.

The vmstat(1)/top(1) commands are useful at monitoring system resources, and the man pages do show you how to interpret the results.

So after doing some more reading, I found a post on a NetBSD mailing list where Chuck Silvers explains how he renamed a few VM related sysctl's (..the old versions are still used by OpenBSD, max values are hard-coded defines.. no knobs).

If I understand all of this sufficiently, the kernel behaves differently depending on how the system is being used.. adapting as it goes along.. the services that knasbas utilizes aren't demanding large amounts of memory, so the majority of available memory is being reserved for other things.

I don't pretend to understand it all, because it's complicated.. using the above optimization guide on OpenBSD is NOT recommended though, the defaults will most likely be quite adequate for your needs.