iMacri tips

VERSION BUILD=7030862
SIZE X=1360 Y=768
TAB T=1
URL GOTO=http://www.lexisnexis.com/hottopics/lnacademic/?shr=t&sfi=AC00NBEasySrch
FRAME F=2
TAG POS=1 TYPE=A ATTR=TXT:Power<SP>Search
TAG POS=1 TYPE=TEXTAREA FORM=NAME:searchForm ATTR=ID:terms CONTENT=acorda<SP>Pharmaceuticals<SP>stock<SP>offering
TAG POS=1 TYPE=SELECT FORM=NAME:searchForm ATTR=ID:dateSelector1 CONTENT=%from
TAG POS=1 TYPE=INPUT:TEXT FORM=NAME:searchForm ATTR=ID:fromDate1 CONTENT=1/1/2000
TAG POS=1 TYPE=INPUT:TEXT FORM=NAME:searchForm ATTR=ID:toDate1 CONTENT=1/1/2010
DS CMD=LDOWN X=223 Y=413 CONTENT=
DS CMD=LUP X=223 Y=413 CONTENT=
DS CMD=KEY X=223 Y=413 CONTENT=business<SP>wire
WAIT SECONDS=2
DS CMD=LDOWN X=223 Y=431 CONTENT=
DS CMD=LUP X=223 Y=431 CONTENT=
TAG POS=1 TYPE=INPUT:SUBMIT FORM=ID:searchForm ATTR=VALUE:Search

Useful Sites

http://www.allmyfaves.com/

 

Technet Cloud

http://dpetechnet.cloudapp.net/Home.aspx

IT Books Online

http://it-ebooks.info

 

Configuring pfSense for Multi-WAN

Parse error: syntax error, unexpected T_VARIABLE in \ /usr/local/apache/htdocs/stat/config.inc.php on line 25

Error:

Parse error: syntax error, unexpected T_VARIABLE in  \
/usr/local/apache/htdocs/stat/config.inc.php on line 25

Solution:

put a ";" at the end of hostfile var

A basic template for website Search Engine Optimisation

Here are some basic tips on optimising your site for Google and other search engines.

Use keywords:

• in your META keywords (128 characters max)


• in your META description (keep keyword close to the left but in a fill sentence).


• in the page title at the far left but possibly not as the first word


• in the first portion of the page (first sentence of the first full paragraph)


• in an H3 or larger tag heading


• in bold in the lower half of the page (anywhere but the first usage on page)


• in italic in the lower half of the page (anywhere but the first usage on page)


• in the URL (directory name, filename or domain name). Do not duplicate the keyword in the URL


• in an image filename useed on the page


• in image ALT attribute


• in image TITLE attribute


• in link TITLE attribute


• in the filename of your external CSS javascript files


• in a link to a site that has a PageRank of 8 or better

Other optimisation tips:

• Use "last modified" headers if you can


• Validate your HTML. Google's parser will miss parts of web pages if they contain simple HTML errors


• Wherever possible keep the page as .html or .htm extension


• Keep the HTML below 20K. 5-15K is the ideal range


• Keep the ratio of text to HTML very high. Text should outweight HTML by significant amounts

Password protecting a directory in Webmin

rmally we use .htaccess and .htpassword files for setting up password protection for accessing certain pages/folders/directories.

In Webmin, there is an option called "Password protecting a directory" set up for you.

Below are the easy steps to password protect a directory using Webmin:

1) login in to the Webmin interface

2) Main menu -> choose "Others" -> choose "Protected Web Directories" -> "Add protection for a new diretcory"
3) in settings:

Directory path: select the path/directory which you want to protect
File containing users: if any, or choose automatically

File containing groups: if any, or choose None

Password encryption: choose the encryption type

Authentication realm: the name will appear in login box, ex: "Admin Area"

Users to allow: put the username you want to setup in "Only Users:" field

4) click the "Create" button

5) in the next page, you can add/edit password for this user, then click submit/save button. It's done!

Site down

http://www.isitdownrightnow.com

Squid as a transparent proxy over ssl https

Setting up squid as a transparent proxy is fairly an easy job. If we Google for “how to set up squid as a transparent proxy” Google renders a lots of links for our reference. But it is commonly seen that when we are using transparent proxy we are unable to connect to https connection like Gmail and many more sites which https protocol for security concern. Sites which use http protocol can easily open.

Let’s understand first how squid proxy works in transparent mode. While setting up squid as a transparent proxy we can forward the entire request coming from port 80 to squid server’s port i.e. 3128 by default. When we talk about port 80 it means http protocol. What if we request for Gmail who uses https protocol and this protocol by default send request to port 443 of squid’s port, and we iptable firewall rules to forward traffic from port 80 to port 3128 and we forget about port 443 which is used by https protocol and squid is http proxy server. Now many folks may think it’s easy and forward all traffic coming from port 443 to squid port 3128.  No it won’t work.  Because https connection establishes a secure connection over the network and for that it uses certificate and public key private key pairs. And first of all I thanks God for RSA and DSA algorithm as it is not so easy to decrypt data which is encrypted by use of this algorithm. Squid proxy is a middle man who changes packets header and route traffic to internet world. So what we have to do is to create certificate and public key private key pair for internal network which can be used by squid client and squid server and later squid server can route your traffic to internet world. To yield faster results it is better to sign certificate from CA. self signed certificates are little bit slowing the connection. As in a transparent mode encryption and decryption done twice so it may yields result slow so I advised you to keep patience.

Steps are:

1. iptables  -t nat -A PREROUTING -i eth0  -p tcp --dport 80 -j REDIRECT --to-port 3128


2. iptables  -t nat -A PREROUTING  -i eth0 -p tcp --dport  443 -j REDIRECT --to-port 3130

Certificate and public key private key generation.

1. openssl genrsa -des3 -out server. Key 1024


2. openssl req -new –key -out server.csr


3. openssl req -new -key server. Key -out server.csr

Steps to remove passphrase

1. cp server. Key server. Key.old


2. openssl rsa -in server. Key.org -out server. Key

Create server certificate

Openssl x509 -req -days 365 -in  server.csr -sign.key -out server.crt

Now make some changes to squid.conf file

1. http_port 3128 transparent


2. https_port 3130 transparent cert=/”path to server.crt” key=/”path to server.key”.

Another easy way to create certificates and public key private key pair is using genkey utility. In order to use that you have crypto-utils package install on your machine.

Steps are:

1. #yum -y install crypto-utils


2. genkey -days 365 squidserver.hostname.com


3. Hit next.


4. Select number of bits for data encryption. Default is 1024. This command will generate random bits.


5. Generate the certificate.


6. I will suggest you to never used passphrase for key, because if u assigns passphrase to key then along with public key we need to share passphrase.


7. Certificate and key are stored at /etc/pki/tls/certs/ and /etc/pki/tls/private/


8. In squid.conf make necessary change like this

http_port 3128 transparent

https_port 3130 transparent cert=/etc/pki/tls/certs/squidserver.hostname.com.crt key=/etc/pki/tls/private/squidserver.hostname.com.key.

In order to run it in a proper way the desired way that we want we also need to configure BIND DNS for local intranet along with forwarders ON and in forwarder we need to define ISP IP Address. At Client side must define both gateway and DNS (In my Env it is Proxy server.)

How to Stop WordPress Asking for FTP details to Upgrade Plugins

1. First, we need to see what user Apache is running under. Type the following into a New file in any text editor. Save As whoami.php in the /var/www directory (or wherever you set Apache to serve files from):
   

   <?php echo(exec("whoami")); ?>

   
   


2. Open this file in a browser (for instance, localhost/whoami.php). It should reveal who the user is


3. This tells you that the web server is running under the user webuser.
   
   You can now give that user recursive ownership (all subfolders) of your WordPress installation using the command:
   
   chown -hR webuser:webuser /var/mydomain.com/public_html/wordpress/

pfSense: Editing /conf/config.xml file

The ISP's internet conenction runs on port expecting a 10MB Full-duplex device to be plugged into it. The WAN interface on our PFSense box is a 10/100 NIC, which when uplinked without making any configuration changes, I found that I was only getting about 25% of the capacity I was expecting. The only way to force the WAN interface to 10MB/Full-duplex is via the /conf/config.xml file. There are two way to edit this… one is using vi from SSH.

To enable SSH do this from the PFSense web-interface:
Click System>Advanced>Secure Shell, Enable Secure Shell

Even if you prefer to use the PFSense web-interface to edit your config.xml file (make a backup copy first), the shell came in handy a few times throughout my configuration process. The other option to edit the config file is using the editor in the PFSense web-interface.

The editor is available here:
Diagnostics>Edit File. The Load/Save path is “/conf/config.xml”.

Scroll down until you find the tag. Then remove the lines that start with <media/> and <mediaopt/> and replace them with ones that say this:

<media>10baseT/UTP</media>
<mediaopt>full-duplex</mediaopt>

Then click Save. You can check to see if this took effect by clicking Status, Interfaces. The WAN interface should now read “10baseT/UTP ”. This change should take effect immediately – if not, give the box a reboot (Diagnostics>Reboot System).

Configure IP Phone in Packet tracer

http://www.youtube.com/watch?v=6rQakFGMZRM

RoundCube: Strict Standards: Non-static method PEAR :: setErrorHandling

When installing the messages appear

1 2 3

PHP Strict Standards: Non-static method PEAR :: setErrorHandling () should not be called statically in / installer / utils.php on line 80 PHP Strict Standards: Non-static method rcube_install :: get_instance () should not be called statically in / installer / index.php on line 49

Eliminated as follows:
1. Open the file .. / installer / index.php
2. Find line

1	ini_set ('error_reporting', E_ALL & ~ E_NOTICE);

and change it to

1	ini_set ('error_reporting', E_ALL & ~ (E_NOTICE | E_STRICT));

3. If no, add this line here

1	define ('RCMAIL_CHARSET', 'UTF-8');

Here after this

1	define ('RCMAIL_CONFIG_DIR', INSTALL_PATH. 'config');

Ubuntu Server 12.04 64-bit with Zoneminder 1.25.0 the easy way

http://www.zoneminder.com/wiki/index.php/Ubuntu_Server_12.04_64-bit_with_Zoneminder_1.25.0_the_easy_way

how to install perl in ubuntu

apt-get install libmoose-perl

How To Install and Configure Varnish with Apache on Ubuntu 12.04

About Varnish

---

Varnish is an HTTP accelerator and a useful tool for speeding up a server, especially during a times when there is high traffic to a site. It works by redirecting visitors to static pages whenever possible and only drawing on the virtual private server itself if there is a need for an active process.

Setup

---

To perform the steps in this tutorial, you will need to both have a user with sudo privileges and apache installed on your virtual private server.

To create a user with sudo privileges, go through the third and fourth steps of the initial ubuntu server setup tutorial
Apache can be installed on your VPS with a single command from the apt-get repository.

sudo apt-get install apache2

 

Step One—Install Varnish

---

The varnish site recommends installing the varnish package through their repository.

You can start that process by grabbing the repository:

sudo curl http://repo.varnish-cache.org/debian/GPG-key.txt | sudo apt-key add -

The next step is to add the repository to the list of apt sources. Go ahead and open up that file.

sudo nano /etc/apt/sources.list

Once inside the file, add the varnish repository to the list of sources.

deb http://repo.varnish-cache.org/ubuntu/ lucid varnish-3.0

Save and exit.

Finally, update apt-get and install varnish.

sudo apt-get update
sudo apt-get install varnish

 

Step Two—Configure Varnish

---

Once you have both apache and varnish installed, you can start to configure them to ease the load on your server from future visitors.

Varnish will serve the content on port 80, while fetching it from apache which will run on port 8080.

Let’s go ahead and start setting that up by opening the /etc/default/varnish file:

sudo nano /etc/default/varnish

Uncomment all of the lines under “DAEMON_OPTS”—under Alternative 2, and make the configuration match the following code:

 DAEMON_OPTS="-a :80 \
             -T localhost:6082 \
             -f /etc/varnish/default.vcl \
             -S /etc/varnish/secret \
             -s malloc,256m"

Once you save and exit out of that file, open up the default.vcl file:

sudo nano /etc/varnish/default.vcl

This file tells varnish where to look for the webserver content. Although Apache listens on port 80 by default, we will change the settings for it later. Within this file, we will tell varnish to look for the content on port 8080. The configuration should like this:

backend default {
    .host = "127.0.0.1";
    .port = "8080";
}

 

Step Three—Configure Apache

---

So far we have told varnish that apache ports will be running on 8080. However the default settings for apache are still on port 80. We will correct the discrepancy now.

Open up the apache ports file:

sudo nano /etc/apache2/ports.conf

Change the port number for both the NameVirtualHost and the Listen line to port 8080, and the virtual host should only be accessible from the localhost. The configuration should look like this:

NameVirtualHost 127.0.0.1:8080
Listen 127.0.0.1:8080

Change these settings in the default virtual host file as well:

sudo nano /etc/apache2/sites-available/default

The Virtual Host should also be set to port 8080, and updated line looks like this:

 <VirtualHost 127.0.0.1:8080>

Save and exit the file and proceed to restart Apache and Varnish to make the changes effective.

sudo service apache2 restart
sudo service varnish restart

Accessing your domain should instantly take you to the varnish cached version, and you can see the details of varnish’s workings with this command:

varnishstat

Asterisk on Ubuntu

http://blogs.digium.com/2012/11/14/how-to-install-asterisk-11-on-ubuntu-12-4-lts/

Asterisk GUI

http://www.asteriskguru.com/tutorials/asterisk_gui.html

frontpage-2002-sr1.2.i386 has missing requires of libexpat.so.0

I recently ran into this error on a CentOS server powered by cPanel. I have noticed that there are a lot of issues when cPanel/WHM is installed on CentOS 6.x. Never the less, I am pretty sure a new system admin could spend hours looking for solutions. Hence, here’s is a quick one.

Error

frontpage-2002-sr1.2.i386 has missing requires of libexpat.so.0

Solution

Please follow these steps exactly

1. SSH into your server


2. Open the file /etc/yum.conf in your favorite text editor (nano is what I am using)
   

   nano /etc/yum.conf

   
   


3. You will find a line that starts with “Exclude”, most likely the first line. You will find perl* written in there.


4. Delete the text “perl*” from the line. Note that there would be many extensions listed, you just need to remove “perl*”


5. Save the file


6. Execute “yum update“

That should be all. Your issue should now be fixed. Feel free to commend here if you run into any further errors.

- See more at: http://linuxlantern.com/frontpage-2002-sr1-2-i386-has-missing-requires-of-libexpat-so-0/#sthash.mtcelAQQ.dpuf