ServerBuddies Support Blog

ln: Make links between files

A “hard link” is another name for an existing file; the link and the original are indistinguishable. Technically speaking, they share the same inode, and the inode contains all the information about a
file–indeed, it is not incorrect to say that the inode _is_ the file. On all existing implementations, you cannot make a hard link to a directory, and hard links cannot cross file system boundaries. (These
restrictions are not mandated by POSIX, however.)

“Symbolic links” (”symlinks” for short), on the other hand, are a special file type (which not all kernels support: System V release 3 (and older) systems lack symlinks) in which the link file actually
refers to a different file, by name.

`ln’ makes links between files. By default, it makes hard links; with the `-s’ option, it makes symbolic (or “soft”) links. Synopses:

* If two file names are given, `ln’ creates a link to the first file from the second.

* If one TARGET is given, `ln’ creates a link to that file in the current directory.

Example:

Tags: between, Files, links, ln, Make

LiteSpeed Web Server Installation Steps

Installation Instructions for LiteSpeed Web Server.

Download From : http://www.litespeedtech.com/litespeed-web-server-downloads.html

1. Extract the package at convinent location by using

or

if you are not using the GNU tar

2. Type

3. If you want to install to system directory, you need to become root first.

Type

4. Follow the instruction on the screen.

Tags: Installation, LiteSpeed, Steps, web server

Verifying Installed Packages

Over the course of a system’s normal usage, files get changed. This could be as innocent as simply changing a configuration file in the /etc directory or as problematic as a file being corrupted by a power failure. To assist in the detection of these changes, RPM allows users and administrators to verify the integrity of an installed package.

The command

or

Will verify all installed packages. RPM then computes the MD5 checksum of all files on the disk and compares them to the stored MD5 sums from the original RPMs. The output of the command is a line indicating any files that differ from the versions that were originally installed and a code indicating how the file has changed.

Tags: installed, Packages, rpm, Verifying

Creating the postfix aliases database

Postfix uses a Sendmail-compatible aliases(5) table to redirect mail for local(8) recipients. Typically, this information is kept in two files: in a text file /etc/aliases and in an indexed file /etc/aliases.db. The command “postconf alias_maps” will tell you the exact location of the text file.

First, be sure to update the text file with aliases for root, postmaster and “postfix” that forward mail to a real person. Postfix has a sample aliases file /etc/postfix/aliases that you can adapt to local conditions.

Note: there should be no whitespace before the “:”.

Finally, build the indexed aliases file with one of the following commands:

Tags: aliases, Creating, database, postfix

Checking Postfix file permission/ownership discrepancies

The first line (postfix check) causes Postfix to report file permission/ownership discrepancies.

The second line looks for problem reports from the mail software, and reports how effective the relay and junk mail access blocks are. This may produce a lot of output. You will want to apply some postprocessing to eliminate uninteresting information.

Tags: Checking, discrepancies, file, Ownership, Permission, postfix