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:
You use finger command in order to check user information. What if it's missing?
The official replacement for the original finger command and it’s part of the gnu coreutils package, it is called pinky and it’s available on all systems that use the gnu coreutils.
For this example I will user md5 but in similar way you can use whatever you want in order to create a hash version of your text password.
As a security note, I do not recommend using md5 to generate hash passwords because today it is very easily broken. This is jut a proof of concept.
I got this SMF forum for my wife and is working very well. I am very satisfied with SMF.
However, sometimes you get into trouble with it and the worst part is you do not have much logs to work with. Also, apache logs won't help much either.
You are here because you got this error when trying to run php via command line: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20100525/pdo_mysql.so' - /usr/lib/php5/20100525/pdo_mysql.so: undefined symbol: pdo_parse_params in Unknown on line 0
Also, you probably use Debian Squeeze and you recently did software update.
If yes, read on for a fix.
AIO subsystems in 6.1 and later are loaded by default and not activated. It is implemented as kernel service instead of using special device aio0 as in previous AIX versions. The kernel module tuning (maxservers, minservers, etc.) is implemented via ioo command.
In order to check the available aio tunables, you must use the following command: # ioo -L | grep aio
The moment application initiates the AIO I/O requests, the subsystems are automatically started.
Your zfs was working properly but you have upgraded your system, including the kernel, and your zfs is no more available.
This is normal because zfs was compiled for the other one.
So all you will have to do is to execute the following commands (do not forget of course to install/put in place the needed linux source or headers before that): dpkg-reconfigure spl-dkms dpkg-reconfigure zfs-dkms