No matter the monitorization solution, CPU utilization is important but if you really want to know what is happening with your system, you should look at load average. I will explain below why.
The current CPU utilization does not reflect the actual load of the system because when a host is heavily loaded, its CPU usage doesn't have to be necessary close to or at 100%.
Furthermore, the CPU utilization tends to generate (in monitoring tools) a significant number of false alerts, even if the percentage alert is close to 100%. Explanation follows.
Do you use Transmission?
If yes, I suggest you check your version and update it soon. There are reports that a specific version has been tampered with.
Over the weekend, the first instance of Mac ransomware was found in a malicious update to the Transmission BitTorrent client. Version 2.90 of Transmission downloaded from the Transmission website was infected with "KeRanger" ransomware.
It is simple and that is why I will be very straight.
The configuration file for grub2 is /boot/grub/grub.cfg, but you do not have to edit that file directly because it is generated by update-grub command and you will loose all your modification on next update.
Many times you can find difficult to perform simple tasks if you do not have the appropriate documentation, or you are not searching it correctly :)
It happened to me the other day: I had to rename a vm in Citrix Xen without XenCenter. After few readings, I discovered!
I know, you have XenCenter and everything is easily done from there.
But what happens if you are not able to use it? Time to fire up the command line :)
In the example below, we will change the memory from 256M to 1G.
Citrix Xen has a way to migrate the machines from one host to another via xe vm-export and xe vm-import commands but there are situations when this won't work.
For example, if the source disk is in bad shape and there are bad (unreadable) blocks on your vm's disks, the xe vm-export command will be unsuccessful with the following error:
I was forced the other day to shutdown a machine via command line and my surprise was to get an error during the execution: VM didn't acknowledge the need to shutdown.
The error is quite convincing and full of useful stuff (NOT) but it's there and you cannot get past it without some extra parameters.
Read on for the solution.
I don't remember exactly when I have installed rEFIt (I did it only once) but I know I am using it without any problems since around 2006 and it went trough 2 laptops and several OSX versions already. The beauty of OSX upgrades and Time Machine.
After installing El Capitan, I was still using it without problems (well, just a small one but no biggie - will be mentioned a bit later), but also with SIP enabled! Will explain about SIP too.
Launchd is designed to start System and Users daemon/agents located in the following places:
~/Library/LaunchAgents - Per-user agents provided by the user /Library/LaunchAgents - Per-user agents provided by the administrator /Library/LaunchDaemons - System-wide daemons provided by the administrator /System/Library/LaunchAgents - Per-user agents provided by Mac OS X /System/Library/LaunchDaemons - System wide daemons provided by MAC OS X
You have a bunch of applications designed to show you temperatures and fan speeds in graphical environment. Some are free but most of them are paid.
But what happens if you need something in command line? Well, it is even better because you can find many free powerful tools.
One of them is iStats. Below you will learn how to install and use it.
Prior to OS X 10.10 Yosemite, you were able to start rc.local script via rc..
That is gone and you have to use launchd.
This tutorial assumes you have already your rc.local script in (example) /etc/rc.local and it is executable and properly populated with your desired commands.
So, without writing too much, below is my example of launchd script: