Tag Info

New answers tagged

0

The microcode packages are basically patches to the CPU, fixing problems that have been detected since the CPU was manufactured. You only need to install the package related to the brand of CPU in the system (i.e. installing amd64-microcode on a system with an Intel processor makes no sense. In any case it can't hurt to install the appropriate microcode ...


1

The /sys filesystem holds a nice overview of this information. Here is an example from an SMP quadcore box with Hyperthreading: # grep . /sys/devices/system/cpu/cpu{,1}?/topology/thread_siblings | tr : \\t | sed 's,^, ,' /sys/devices/system/cpu/cpu0/topology/thread_siblings 00000000,00000101 /sys/devices/system/cpu/cpu1/topology/thread_siblings ...


0

Turns out to be some crazy interrupt on Macbook pros. http://loicpefferkorn.net/2015/01/arch-linux-on-macbook-pro-retina-2014-with-dm-crypt-lvm-and-suspend-to-disk/


2

You can try to use nmon instead of htop. The reason for it might be a program, that has high amount of HDD traffic, so that the CPU isn't actually used, but waiting for device sync. Or maybe it isn't actually a processes but a old/damaged HDD. In nmon this is showed seperated in the CPU usage. I don't know if htop does.


3

If you press c while in top then the command will be expanded to show the full command used to start the process. You can also take the PID and run: ps -ef | grep $PID Or: cat /proc/$PID/cmdline


1

Run a process this way: time scriptname # or time command It will report the sum of children plus parent As soon as you add the word daemon, the picture changes. top will show the approximate value, top -p [pid] You can also read /proc[pid]/stat.utime and friends (utime, stime, cutime, cstime (children start with c) ) with C or perl or python. ...


1

I've run these services on a machine with 2x1GHz cores with 256MB RAM but I would expect that if this is your only service you have, you would only need something like dual-core 500MHz+ (one would work but needs to be a bit faster) CPU and 128MB RAM.


2

From the VirtualBox manual: 12.4.1. Linux guests may cause a high CPU load Some Linux guests may cause a high CPU load even if the guest system appears to be idle. This can be caused by a high timer frequency of the guest kernel. Some Linux distributions, for example Fedora, ship a Linux kernel configured for a timer frequency of 1000Hz. We ...


5

Rather than testing for a valid executable, it's probably best to test what the current architecture is, then select the proper executable based on that. For example: if [ $(uname -m) == 'armv6l' ]; then tool-rpi else tool-osx fi However, if testing the executable is what you really want to do, GNU file can tell you the architecture of an ...


2

On Linux glibc, one hack you could use to test whether an dynamically linked executable would run successfully but without actually running it would be to set LD_DEBUG=help in its environment. It it's good it will emit a help message (which you ignore) and exit successfully, and if it is invalid then you will get an error. Unfortunately this is specific to ...



Top 50 recent answers are included