Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
I have just upgraded to 0.7.4 on a Debian squeeze system. This is running on a Seagate Dockstar, which has 128 MB of RAM and 999 MB of swap. Currently the output of htop is
See "man top" for the exact meaning of these numbers.
EDIT:
VIRT stands for the virtual size of a process, which is the sum of memory it is actually using, memory it has mapped into itself (for instance the video card’s RAM for the X server), files on disk that have been mapped into it (most notably shared libraries), and memory shared with other processes. VIRT represents how much memory the program is able to access at the present moment.
RES stands for the resident size, which is an accurate representation of how much actual physical memory a process is consuming. (This also corresponds directly to the %MEM column.) This will virtually always be less than the VIRT size, since most programs depend on the C library.
See "man top" for the exact meaning of these numbers.
Yes, I remember
I'm just used to looking at htop's overall stats, which are a different thing I guess. It sort of confused me how VIRT could be greater than the total amount of memory the machine has plus the total amount of swap in use. But yes, it does match the output of top.
Thank you for your reply. sab and sickbeard still working perfectly.