Generally speaking, many search engines like Google, MSN, and Yahoo like to see your URLs be as pretty as possible. Using applications like PHP will often produce URLs that look like this: http://somesite.com/index.php?section=section1&data=test. These URLs are typically frowned upon by the search engines and can produce mixed results when attempting to achieve the highest search engine ranking.
There are two methods we can use to make our URL’s a bit more friendly. Many applications today already provide pre-packaged .htaccess files. It’s important for me to explain that there are two methods for setting up mod_rewrite rules. The first (and most common) method is to use a file called “.htaccess” placed in the root directory of your web site. This file is read in to the Apache configuration in real time (The AllowOverride option in your Apache configuration controls this). We’ll cover the .htaccess method here.
The .htaccess Method
This is the most common way to implement mod_rewrite rules. First, open a text file with your favorite editor (if you do not have shell access simply use notepad or vi on your local machine). Remember that a dot (.) before the file name designates this file as hidden in Linux.
For our example we’re going to redirect http://somesite.com/index.php?section=section1&data=test to look like this: http://somesite.com/section1/test.
- Edit the .htaccess file you wish to
# vi /var/www/html/.htaccess
- Place the following in the new .htaccess file:
RewriteRule ([^/]+)/([^/]+)?$ index\.php?section=$1&data=$2 [L]
- Save the file and exit your editor.
(* Note: If you upload this file with an FTP/SCP program your file will not appear as it is hidden, if you need to delete the file due to a misconfiguration, issue “DELE .htaccess” in the directory you uploaded the file.)
The [L] directive tells mod_rewrite to redirect the request with a 301 redirect.
- I receive a 500 server error after uploading.
Check to make sure no typo’s were made. Check the apache error_log for any clues.
- The redirect does not take place but the site still shows.
This is usually because your host does not support mod_rewrite or is not allowing .htaccess files. To check if .htaccess is being parsed open a new .htaccess and put the following inside:
Redirect /test “http://www.google.com”
If this works you can safely assume that .htaccess files are being parsed.
As we continue to find Linux loaded on more and more consumer-based PC’s the reality of Linux everywhere has come to fruition. I’m relatively excited that Ubuntu is being endorsed by companies like Dell. As more and more PC’s ship with Linux pre-loaded it’s almost necessary to become acquainted with the Linux shell. For those of you from the Microsoft days I would almost consider the Linux shell to be the DOS of Windows 3.1/95/98 (WinXP just emulated the shell). In the blurb below I try to make correlations to Windows commands to help you grasp what each command does.
Anyway, here ten of the commands I think you should know when using Linux as a first-time user. Note that when typing these commands the # sign symbolizes the shell prompt and you shouldn’t type it 🙂
I think the first command anyone should know is man. Man is short for "manual". This command provides you with details about any command (You can even "man man" from the command). Think of this as the F1 key in your standard Windows installation.
# man <command>
# man ls
Type "q" on the keyboard to exit.
Now that we know how to see what commands do, we need to know how to see files on the file system. The ls command shows you a listing of all files in a given directory. If no directory is specified, the command returns a listing of files and directories in the current working directory (CWD). Specify a directory after ls and receive a listing of that directory.
# ls <directory,optional>
# ls /etc
If you want to hang with the pros you should probably take a short amount of time and pick up vi. VI is the Linux text editor of choice for the command line. Think of VI as your quick notepad in Windows. Specify a file after the vi command to open the file. Use the arrow keys to navigate the text file.
Use the following basic commands to navigate vi:
a.) /<search string> (searches for a string)
b.) :w (writes the open file)
c.) :q! (quit without saving changes)
d.) :wq (write changes and quit)
e.) :q (quit vi)
Type "i" to enter editing mode. Hit escape after making your changes to enter the commands above.
# vi <file to edit>
# vi /etc/fstab
Have you ever lost it? What if you never had it? Enter find. Find’s only similarity, to that annoying puppy in Windows XP, is that it will find your files. Other than that, this utility does its job effortlessly.
# find <path> -name <name of file>
# find / -name foo.txt
(This command finds "foo.txt" anywhere starting with the root "/" of the file system)
This utility shows the contents of a given file. Think of this command as the Windows equivalent "type". Specify the name of the file you wish to display after the command and … presto!
# cat <file to output>
# cat /etc/fstab
This command receives input from STDIN (Standard Input) and allows you to page through the output. This is useful with the command mentioned above. What if you have too much data for your shell’s output buffer? You can’t scroll up. Enter less. Simply pipe the output of your program to less and it’ll show you a scrollable, searchable result. Use the space part to page down. Use the arrow keys to navigate up and down and type "/<search string>" to search.
# <command> | less
# cat /etc/exim.conf | less
Grep allows you to search a file for a string. It’s very simple to use. After executing your grep, each line is printed which matches your string.
# grep "string" <file>
# grep "sda" /etc/fstab
- rm, cp and mv
Here are a few commands you can’t live without: rm, cp, and mv.
To remove a file use this syntax:
# rm <file>
To remove a directory and its files contained:
# rm -rf <path to directory>
To copy a file simply use the following syntax:
# cp <source> <destination>
To rename or move a file use the following syntax:
# mv <source> <destination>
PS or "process list" shows you a list of all running processes. The commonly used (at least for me) command with flags is:
# ps aux
This command shows you a list of all processes, which user they are running as and the command (truncated).
Linux is a very secure Operating System. Its roots of security lay in its strict ACL (Access Control List) settings. Linux uses chmod (change file access permissions) and chown (change file owner and group) to modify user settings and ownerships.
There are many ways to use chmod but we’ll explain the simplest.
# chmod <modes> <file/directory>
If we were to create a shell script and we wanted to set it executable we would perform the following chmod:
# chmod +x script.sh
If we wanted to set the file read/write/execute we could use this command:
# chmod +rwx script.sh
Chown simply changes the owner and/or group of the file. The old way of changing the ownerships was like this:
# chown user.group <file/directory>
To the best of my knowledge this command works but it is a bit outdated. Now simply replace the "." with ":" so the command looks like this:
# chown user:group <file/directory>
I want to change /etc/fstab to be owned by user award and group foogroup. (Don’t do this really hehe!) I would use this command:
# chown award:foogroup /etc/fstab
There are quite a few commands available in the Linux world. It’s always a good idea to be comfortable with the command line. The command line becomes easier as you use it (I’ve been living in it for almost 10 years now). The power and flexibility the command line offers is unmatched by any GUI. As with everything I recommend that you learn something from the inside out. That being said, start out with the command prompt and play around. Load up a VM (Virtual Machine) with Ubuntu or CentOS and play around. Check out this article to see how to load VMware Server Beta and get started today.
There are a few ways to list all ports open and to show which daemons are listening. Simply run one of the two commands:
# lsof -i | grep "(LISTEN)"
# netstat -tupan | grep "LISTEN"
I believe this to be a cleaner output
Everyone knows there are tons of people out there chasing storms. This fellow happened to build his own tornado cruiser to keep up with them. This sounds like a DIY project waiting to be written up 😛
Backups are most important when you really need them. Most hosting companies, business and personal users implement their backups with traditional RSYNC. Since RSYNC can be piped over SSH it serves as a very secure way to perform backups of critical files. Using Rsnapshot can provide even more flexibility with snapshot capabilities.
What if you have thousands of files? What about millions of files? RSYNC becomes very cumbersome as it has to walk every directory and every file to compare checksums, modified times and contents. RSYNC literally grinds to a halt as it attempts to tally file counts greater than 500,000 (at least on our system systems).
So what’s the solution? For many years we have been performing backups at the file level. Performing backups at the file level adds latency and can be very time consuming. The new technology is CDP (Continuous Data Protection). This technology, in fact, is not very new at all. Faster Internet connections enable us to perform backups at the sector-level over the wire. Sector-level backups are so much faster because only the changed sectors are transmitted.
R1Soft has pioneered this technology in the Linux market. Their kernel device driver (the heart of their backup agent) actually tracks block-level changes in real time. The next time the backup kicks off the agent knows exactly what blocks have changed. You might be thinking to yourself "That has to add overhead!" but, in reality, it uses no more than 10MB of physical RAM per 100GB the device driver monitors.
Image level backups are so fast we can back up our web servers in less than 5 minutes every 2 hours. These backups are less CPU and disk intensive than any file-level backup can offer.
To test drive image-level backups with R1Soft technology, visit WebHostBackups.com for more information.