Install ioncube in ubuntu

1. Download ionCube loaders

sudo wget http://downloads.ioncube.com/loader_downloads/ioncube_loaders_lin_x86.tar.gz


2. Extract

sudo tar zxvf ioncube_loaders_lin_x86.tar.gz


3. Move to a permanent location

sudo mv ioncube /usr/local/


4. Add reference to your php.ini file (sudo pico /etc/php5/apache2/php.ini)

zend_extension = /usr/local/ioncube/ioncube_loader_lin_5.2.so


There are a few versions of the loader in the tar archive. Use the one that matches your PHP version.

5. Restart apache

sudo /etc/init.d/apache2 restart

6. check installation using following command:
php -v
you should see following output:

PHP 5.1.6 (cli) (built: Apr 7 2009 08:00:04)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
with the ionCube PHP Loader v3.1.34, Copyright (c) 2002-2009, by ionCube Ltd.

Cloning VMs on Linux Hosts with VMWare Server 2.0

think it’s a MAJOR pain not having a “clone” feature in VMWare Server without using Virtual Infrastructure, so I made my own Linux shell scripts to do it.

The clone script does a straight clone of a VM. It copies the directory, renames the files and tweaks all the text inside the files by using sed to replace the old name with the new one, then sets all the permissions to what they would be if you created a new VM.

The rename script basically does all but copy it. This is handy for if you tried to rename a directory manually or attempted a manual copy and then found it still shows up under the old name in the web console. Remember this one assumes you have already renamed the directory to the new name and it MUST be the same as what you intend for the new name to be.

Both work the same way… scriptname <old name> <new name>

You can use quotes around the names if there are spaces, I went to great lengths to make sure it would still work with spaces in names (although I personally hate spaces).

Save the scripts to the base directory where your VM’s are, “standard” location is “/var/lib/vmware/Virtual Machines”. Make executable with chmod +x <scriptname>.

Once ran, add the new/renamed VM to the web console and choose “I copied it” or “I moved it” as appropriate.

These scripts are offered free to everyone to use, modify, or do anything else you want with except take credit for the original version. Absolutely no warranty or guarantee of any kind on the part of anyone that they won’t hose your VMs or even your whole system.

If I understand correctly how the split disks work, the 3rd file attached (clone-split-disk.sh) should work for those VM’s. I have not tested it myself and will likely not get a chance anytime soon, so I will rely on feedback from the community for any near-future tweaking. This is really just a change to one line (line 34) in the file – in the original we exclude the binary .vmdk file from parsing to find-and-replace since this is how single-disk-file versions are saved; in this version we exclude -f???.vmdk where “?” is a number between 0-9 (i.e. files like -f001.vmdk, -f002.vmdk, etc) while we parse the .vmdk file since with split disks, the .vmdk is a text file describing the -f???.vmdk binary disk files. IF you use a combination of split disks and single-file disks, probably neither one of these will work – maybe in a future version I will be able to merge the two scripts and add logic to tell the disk types apart.

clone_vm
change_name
clone-split-disk

How to Fix “Spooler Subsystem App has encountered a problem and needs to close”

Microsoft’s Solution from KB article 324757

To resolve this issue, follow these steps:

1. If the Lexmark print service is installed on your computer, turn off the LexBce Server service. To do this, follow these steps:

a. Click Start, right-click My Computer, and then click Manage.
b. Expand Services and Applications, and then click Services.
c. In the right pane, right-click LexBce Server, and then click Properties.
d. On the General tab, in the Startup type list, click Disabled.
e. Under Service status, click Stop, and then click OK.
f. Right-click the Print Spooler service, and then click Start (if it is stopped).
g. Quit Computer Management.

2. Test whether the issue is resolved. If the issue is resolved, you do not have to follow the remaining steps. If the issue is not resolved, go to step 3, and then follow the remaining steps.

3. Start the computer in Safe Mode

4. Start Microsoft Windows Explorer, and then delete all the files and the folders in the following two folders (where C: is the drive where you have Windows XP installed):

C:WindowsSystem32SpoolPrinters
C:WindowsSystem32SpoolDriversw32x86
5. Start Registry Editor. To do this, click Start, click Run, type regedit in the Open box, and then click OK.

6. Locate and expand the following registry key:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintEnvironmentsWindows NT x86

View the list of subkeys. There should only be the following subkeys:

Drivers
Print Processors
7. If there are any subkeys other than the subkeys that are listed in step 6, follow these steps

a. On the File menu, click Export.

b. In the File Name box, type a descriptive name for this key, and then click Save–for example, type WindowsNTx86regkey.

You can use this backup of the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintEnvironmentsWindows NT x86 registry key to restore the key if you experience any issues after you complete this procedure.

c. Delete all the subkeys other than the subkeys that are listed in step 6. To do this, right-click each subkey that is not on the list, and then click Delete. Click Yes when you are prompted to confirm the deletion.

8. Locate and then expand the following registry key:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintEnvironmentsWindows NT x86Drivers

The registry entries for the printer drivers that are installed on the computer are stored in the Version-x subkey or subkeys, where x is a number (typically 2 or 3).

9. Expand the Version-x subkey or subkeys, and then delete the printer driver entries. To do this, right-click each printer driver subkey, and then click Delete. Click Yes when you are prompted to confirm the deletion.

10. Locate and then expand the following registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors

View the list of subkeys. There should only be the following subkeys for the default print monitors:

BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
11. If there are any subkeys other than the subkeys that are listed in step 10, follow these steps:

a. On the File menu, click Export.

b. In the File Name box, type a descriptive name for this key — for example, type MonitorsRegkey, and then click Save.

You can use this backup of the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlPrintMonitors registry key to restore the key if you experience any issues after you complete this procedure.

c. Delete all the subkeys other than the subkeys that are listed in step 10. To do this, right-click each subkey that is not on the list, and then click Delete. Click Yes when you are prompted to confirm the deletion.

12. If you have a local printer attached, disconnect the printer cable from the computer, and then restart the computer.

13. Verify that the Print Spooler service is running. To do this, follow these steps:

a. Click Start, right-click My Computer, and then click Manage.
b. Expand Services and Applications, and then click Services.
c. In the right pane, right-click the Print Spooler service, and then click Start (if it is stopped).
d. Quit Computer Management.

14. If you have a local printer attached, reconnect the printer cable to the computer, add the printer that you want, and then try to print a test page. To add your printer, follow these steps:

a. Click Start, and then click Printers and Faxes.
b. Click Add a printer.
The Add Printer Wizard starts.
c. Follow the instructions in the Add Printer Wizard to install the printer that you want.

Tags: Print Spooler, Printer

VMWare – Guest cannot browse Internet

I think I figured it out. It isn’t related to SLlinux, nor to port 443, nor to VMWare and the FC5 port directly, but a combination of the Fedora port and VMware settings. It is related to the MTU setting consistancy between the virtual machine, FC5 and the site in question. For some reason the FC5 was set to 1492 and not 1500 as set under FC3. For this reason some of the HTTPS sites, I assume, require 1500 mtu. All I did was set Fedora’s eth0′s MTU setting to 1500 (ip link set eth0 mtu 1500) and it works fine. Weird. I could be wrong, but I think that was the problem. At least now it works. I got this hint from the guys at Fidelity. They thought it was unrelated, but apparently it is.

Maximum Transmission Unit(MTU), the largest physical packet size, measured in bytes, that a network can transmit. Any messages larger than the MTU are divided into smaller packets before being sent.By optimizing the MTU setting you can gain substantial network performance increases, especially when using dial-up modem connections.

Default MTU Size for Different Network Topology

To change the MTU of an interface on GNU/Linux, you just need to use ifconfig command to do so, like this for example

sudo ifconfig eth0 mtu 1492

To change it permanently on Debian, put it in the /etc/network/interfaces file .where almost all network parameters are found. To do this, just add a line mtu to the definition of your interface and save the file.

sudo gedit /etc/network/interfaces

Example

iface eth0 inet static
address 192.168.0.1
network 192.168.0.0
gateway 192.168.0.254
netmask 255.255.255.0
mtu 1492

Daiup Users

For dialup users: the Maximum Transmission Unit (MTU) value can be changed within the file
/etc/ppp/options