Linux Specialist

Threat Modeling and Risk Management Linux

2010-05-07T01:31:00.000-07:00

Since this book is about building secure Linux Internet servers from the ground up, you’re probably expecting system-hardening procedures, guidelines for configuring applications securely, and other very specific and low-level information. And indeed, subsequent chapters contain a great deal of this.
But what, really, are we hardening against? The answer to that question is different from system to system and network to network, and in all cases, it changes over time. It’s also more complicated than most people realize. In short, threat analysis is a moving target.
Far from a reason to avoid the question altogether, this means that threat modeling is an absolutely essential first step (a recurring step, actually) in securing a system or a network. Most people acknowledge that a sufficiently skilled and determined attacker[1] can compromise almost any system, even if you’ve carefully considered and planned against likely attack-vectors. It therefore follows that if you don’t plan against even the most plausible and likely threats to a given system’s security, that system will be particularly vulnerable.
[1] As an abstraction, the "sufficiently determined attacker" (someone theoretically able to
compromise any system on any network, outrun bullets, etc.) has a special place in the
imaginations and nightmares of security professionals. On the one hand, in practice such people
are rare: just like "physical world" criminals, many if not most people who risk the legal and social
consequences of committing electronic crimes are stupid and predictable. The most likely
attackers therefore tend to be relatively easy to keep out. On the other hand, if you are targeted
by a skilled and highly motivated attacker, especially one with "insider" knowledge or access,
your only hope is to have considered the worst and not just the most likely threats.
This chapter offers some simple methods for threat modeling and risk management, with real-life examples of many common threats and their consequences. The techniques covered should give enough detail about evaluating security risks to lend context, focus, and the proper air of urgency to the tools and techniques the rest of the book covers. At the very least, I hope it will help you to think about network security threats in a logical and organized way.

Change Text on XP Start Button XP Trick

2010-05-07T01:28:00.000-07:00

Step 1 - Modify Explorer.exe File

In order to make the changes, the file explorer.exe located at C:\Windows needs to be edited. Since explorer.exe is a binary file it requires a special editor. For purposes of this article I have used Resource Hacker. Resource HackerTM is a freeware utility to view, modify, rename, add, delete and extract resources in 32bit Windows executables and resource files (*.res). It incorporates an internal resource script compiler and decompiler and works on Microsoft Windows 95/98/ME, Windows NT, Windows 2000 and Windows XP operating systems.

get this from h**p://delphi.icm.edu.pl/ftp/tools/ResHack.zip

The first step is to make a backup copy of the file explorer.exe located at C:\Windows\explorer. Place it in a folder somewhere on your hard drive where it will be safe. Start Resource Hacker and open explorer.exe located at C:\Windows\explorer.exe.

The category we are going to be using is "String Table". Expand it by clicking the plus sign then navigate down to and expand string 37 followed by highlighting 1033. If you are using the Classic Layout rather than the XP Layout, use number 38. The right hand pane will display the stringtable. We’re going to modify item 578, currently showing the word “start” just as it displays on the current Start button.

There is no magic here. Just double click on the word “start” so that it’s highlighted, making sure the quotation marks are not part of the highlight. They need to remain in place, surrounding the new text that you’ll type. Go ahead and type your new entry. In my case I used Click Me!

You’ll notice that after the new text string has been entered the Compile Script button that was grayed out is now active. I won’t get into what’s involved in compiling a script, but suffice it to say it’s going to make this exercise worthwhile. Click Compile Script and then save the altered file using the Save As command on the File Menu. Do not use the Save command – Make sure to use the Save As command and choose a name for the file. Save the newly named file to C:\Windows.

Step 2 – Modify the Registry

!!!make a backup of your registry before making changes!!!

Now that the modified explorer.exe has been created it’s necessary to modify the registry so the file will be recognized when the user logs on to the system. If you don’t know how to access the registry I’m not sure this article is for you, but just in case it’s a temporary memory lapse, go to Start (soon to be something else) Run and type regedit in the Open field. Navigate to:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon

In the right pane, double click the "Shell" entry to open the Edit String dialog box. In Value data: line, enter the name that was used to save the modified explorer.exe file. Click OK.

Close Registry Editor and either log off the system and log back in, or reboot the entire system if that’s your preference. If all went as planned you should see your new Start button with the revised text.[/b]

Single Users vs. Multiusers vs. Network Users

2010-04-17T10:06:00.001-07:00

Single Users vs. Multiusers vs. Network Users
Windows was designed according to the “one computer, one desk, one user” vision ofMicrosoft’s
cofounder Bill Gates. For the sake of discussion, I’ll call this philosophy single-user. In this
arrangement, two people cannot work in parallel running (for example) Microsoft Word on the
same machine at the same time. Using Terminal Services in Windows 2000 or Windows XP
allows remote use of one computer from another but is still bound by the single-user paradigm.
The Windows .NET Server products, which are unfinished as of this writing, continue to add
terminal features to enable more than one user to access the server simultaneously.
Linux borrows its philosophy from UNIX. When UNIX was originally developed at Bell
Labs in the early 1970s, it ran on a PDP-7 computer that needed to be shared by an entire
department. It required a design that allowed multiple users to log in to the central machine at
the same time. Various people could edit documents, compile programs, and do other work
at the exact same time. The operating system on the central machine took care of the “sharing”
details, so that each user seemed to have an individual system. This multiuser tradition
continues through today, on other UNIXs as well. And since Linux’s birth in the early 1990s,
it has supported the multiuser arrangement.

Today, the most common implementation of a multiuser setup is to support servers—
systems dedicated to running large programs for use by many clients. Each member of a
department can have a smaller workstation on the desktop, with enough power for day-to-day
work. When they need to do something requiring significantly more CPU power or memory,
they can run the operation on the server.
Linux, Windows 2000, and Windows .NET Server are all capable of providing services
such as databases over the network. Users of this arrangement can be called network users,
since they are never actually logged in to the server but rather send requests to the server. The server does the work and then sends the results back to the user via the network. The catch in this case is that an application must be specifically written to perform such server/client duties. Under Linux, a user can run any program allowed by the system administrator on the server without having to redesign that program. Most users find the ability to run arbitrary programs on other machines to be of significant benefit.

What Is the GNU Public License?

2010-04-17T10:01:00.000-07:00

What Is the GNU Public License?
The most important thing to emerge from the GNU project has been the GNU General Public
License (GPL). This license explicitly states that the software being released is free, and that
no one can ever take away these freedoms. It is acceptable to take the software and resell it,
even for a profit; however, in this resale, the seller must release the full source code, including any changes. Because the resold package remains under the GPL, the package can be distributed free and resold yet again by anyone else for a profit. Of primary importance is the liability clause: The programmers are not liable for any damages caused by their software. More about GNU and the GPL can be found at http://www.gnu.org.

It should be noted that the GPL is not the only license used by free software developers
(although it is arguably the most popular). Other licenses, such as BSD and Apache, have
similar liability clauses but differ in terms of their redistribution. For instance, the BSD license
allows people to make changes to the code and ship those changes without having to disclose
the added code. (The GPL would require that the added code be shipped.) For more information about other open-source licenses, check out http://www.opensource.org.

ISP’s Primary DNS Server Setup Architecture

2010-04-12T13:55:00.000-07:00

ISP’s Server Architecture

Primary DNS Server:

Partition Table Informtion

Filesystem Size Used Avail Use% Mounted on

/dev/sda1 3.0G 667M 2.2G 24% /

tmpfs 252M 0 252M 0% /dev/shm

/dev/sda5 102M 36M 67M 36% /boot

/dev/sda7 2.4G 33M 2.2G 2% /tmp

/dev/sda2 2.0G 96M 1.8G 5% /var

Packages used for DNS: bind-utils-9.3.1-3, bind-chrootenv-9.3.1-3, bind-9.3.1-3, bind-libs-9.3.1-3.2

Configuration file: /etc/named.conf

# Author: Frank Bodammer, Lars Mueller

# /etc/named.conf

# This is a sample configuration file for the name server BIND 9. It works as

# a caching only name server without modification.

# A sample configuration for setting up your own domain can be found in

# /usr/share/doc/packages/bind/sample-config.

# A description of all available options can be found in

# /usr/share/doc/packages/bind/misc/options.

options {

# The directory statement defines the name server's working directory

directory "/var/lib/named";

# Write dump and statistics file to the log subdirectory. The

# pathenames are relative to the chroot jail.

dump-file "/var/log/named_dump.db";

statistics-file "/var/log/named.stats";

# The forwarders record contains a list of servers to which queries

# should be forwarded. Enable this line and modify the IP address to

# your provider's name server. Up to three servers may be listed.

#forwarders { 192.0.2.1; 192.0.2.2; };

# Enable the next entry to prefer usage of the name server declared in

# the forwarders section.

#forward first;

# The listen-on record contains a list of local network interfaces to

# listen on. Optionally the port can be specified. Default is to

# listen on all interfaces found on your system. The default port is

# 53.

#listen-on port 53 { 127.0.0.1; };

# The listen-on-v6 record enables or disables listening on IPv6

# interfaces. Allowed values are 'any' and 'none' or a list of

# addresses.

listen-on-v6 { any; };

# The next three statements may be needed if a firewall stands between

# the local server and the internet.

#query-source address * port 53;

#transfer-source * port 53;

#notify-source * port 53;

# The allow-query record contains a list of networks or IP addresses

# to accept and deny queries from. The default is to allow queries

# from all hosts.

#allow-query { 127.0.0.1; };

# If notify is set to yes (default), notify messages are sent to other

# name servers when the the zone data is changed. Instead of setting

# a global 'notify' statement in the 'options' section, a separate

# 'notify' can be added to each zone definition.

notify no;

};

# To configure named's logging remove the leading '#' characters of the

# following examples.

#logging {

# # Log queries to a file limited to a size of 100 MB.

# channel query_logging {

# file "/var/log/named_querylog"

# versions 3 size 100M;

# print-time yes; // timestamp log entries

# };

# category queries {

# query_logging;

# };

# # Or log this kind alternatively to syslog.

# channel syslog_queries {

# syslog user;

# severity info;

# };

# category queries { syslog_queries; };

# # Log general name server errors to syslog.

# channel syslog_errors {

# syslog user;

# severity error;

# };

# category default { syslog_errors; };

# # Don't log lame server messages.

# category lame-servers { null; };

#};

# The following zone definitions don't need any modification. The first one

# is the definition of the root name servers. The second one defines

# localhost while the third defines the reverse lookup for localhost.

zone "." in {

type hint;

file "root.hint";

};

zone "localhost" in {

type master;

file "localhost.zone";

};

zone "0.0.127.in-addr.arpa" in {

type master;

file "127.0.0.zone";

};

zone "ns1" IN {

type master;

file "master/ns1.zone";

allow-transfer {202.125.142.117;};

};

zone "142.125.202.in-addr.arpa" IN {

type master;

file "master/rns1.zone";

};

zone "pucit.edu.pk" IN {

type master;

file "master/pucitedu.zone";

allow-transfer {202.125.142.117;};

};

zone "pucitonline.net" IN {

type master;

file "master/pucitnet.zone";

allow-transfer {202.125.142.117;};

};

zone "mapasha.com" IN {

type master;

file "master/mapasha.zone";

allow-transfer {202.125.142.117;};

};

zone "mtexperts.co.uk" IN {

type master;

file "master/mtexpert.zone";

allow-transfer {202.125.142.117;};

};

zone "agiletechnologies.org" IN {

type master;

file "master/agile.zone";

allow-transfer {202.125.142.117;};

};

zone "ktexperts.com" IN {

type master;

file "master/ktexperts.zone";

allow-transfer {202.125.142.117;};

};

zone "completeislam.com" IN {

type master;

file "master/cislam.zone";

allow-transfer {202.125.142.117;};

};

zone "peace.com.pk" IN {

type master;

file "master/peace.zone";

allow-transfer {202.125.142.117;};

};

zone "ghazisolutions.com" IN {

type master;

file "master/ghazi.zone";

allow-transfer {202.125.142.117;};

};

zone "puran.info" IN {

type master;

file "master/puran.zone";

allow-transfer {202.125.142.117;};

};

zone "nms.pucit" IN {

type master;

file "master/nms.zone";

allow-transfer {202.125.142.117;};

};

zone "pucitonline.com" IN {

type master;

file "master/pucitonline.zone";

Allow-transfer {202.125.142.117;};

};

zone "ngnexporters.com" IN {

type master;

file "master/ngnexporters.zone";

Allow-transfer {202.125.142.117;};

};

# Include the meta include file generated by createNamedConfInclude. This

# includes all files as configured in NAMED_CONF_INCLUDE_FILES from

# /etc/sysconfig/named

include "/etc/named.conf.include";

# You can insert further zone records for your own domains below or create

# single files in /etc/named.d/ and add the file names to

# NAMED_CONF_INCLUDE_FILES.

# See /usr/share/doc/packages/bind/README.SUSE for more details.

/var/lib/named/pucitnet

$TTL 2D

@ IN SOA ns1.pucitonline.net. root.pucitonline.net. (

200312121;

3600;

1h );

IN NS ns1

IN NS ns2

ns1 IN A 202.125.142.107

ns2 IN A 202.125.142.117

www IN A 202.125.142.121

pucitonline.net. IN MX 10 mail

mail IN A 202.125.142.115

ftp IN A 202.125.142.121

radius IN A 202.125.142.108

nms IN A 202.125.142.108

/var/lib/named/pucitedu

$TTL 2D

@ IN SOA ns1.pucitonline.net. root.pucitonline.net. (

200312121;

360;

3600;

1h );

IN NS ns1.pucitonline.net.

IN NS ns2.pucitonline.net.

ns1 IN A 202.125.142.107

ns2 IN A 202.125.142.117

www IN A 202.125.142.121

pucit.edu.pk. IN MX 10 mail

mail IN A 202.125.142.122

ftp IN A 202.125.146.174

flypucit IN A 202.125.142.109

moon IN A 202.125.142.97

library IN A 202.125.142.112

alumni IN A 202.125.142.112

lectures IN A 202.125.142.112

Shamil Bank of Bahrain Job A Brighter Future

2010-03-13T00:56:00.000-08:00

Shamil Bank of Bahrain Job A Brighter Future

Linux Dual Booting Issues troubleshooting

2010-02-17T01:36:00.000-08:00

Dual-Booting Issues
If you are new to Linux, you may not be ready to commit to a complete system when you just
want a test drive. All distributions of Linux can be installed on only certain partitions of your
hard disk while leaving others alone. Typically, this means allowing Microsoft Windows to
coexist with Linux.

Because you are focusing on server installations, the text will not cover the details of
building a dual-booting system; however, anyone with a little experience in creating partitions
on a disk should be able to figure this out. If you are having difficulty, you may want to refer
to the installation guide that comes with your distribution or another one of the many available
beginner’s guides to Linux.

Some quick hints: If a Windows 95 or Windows 98 partition currently consumes an entire
hard disk as drive C:, you can use the fips tool to repartition the disk. Simply defragment and
then run fips.exe. If you are using Windows NT/2000 with NTFS and have already allocated
all the disk with data on each partition, you may have to move data around a bit by hand to
free up a partition. Don’t bother trying to shrink an NTFS partition, though; because of its
complexity, it doesn’t like being resized, and doing so will lead to corruption.

You may find using a commercial tool such as Partition Magic to be especially helpful,
because it offers support for NTFS, FAT32, and regular FAT, as well as a large number of
other file system types. Its user interface is also significantly nicer than fips.
If you’re going to be installing a dual-boot system, install Linux last. If you install
Windows last, it will clobber the boot information for your Linux system. If you install Linux
last, it will recognize that you have Windows installed and let you choose which one you want
to boot by default. Linux gets an “A” for citizenship.

Methods of Installation
With the improved connectivity and speed of both local area networks and Internet connections,
it is becoming an increasingly popular option to perform installations over the network rather
than using a local CD-ROM.
In general, you’ll find that network installations become important once you’ve decided to
deploy Linux over many machines and therefore require a fast installation procedure in which
many systems can install at the same time.

Typically, server installations aren’t well suited to automation, because each server usually
has a unique task; thus, each server will have a slightly different configuration. For example, a
server dedicated to handling logging information sent to it over the network is going to have
especially large partitions set up for the appropriate logging directories, compared with a file
server that performs no logging of its own. (The obvious exception is for server farms where
you have large numbers of replicated servers. But even those installations have their nuances
that require attention to detail specific to the installation.)

Because of this, you will focus exclusively on the technique for installing a system from a
CD-ROM. Of course, once you have gone through the process from a CD-ROM, you will find
performing the network-based installations to be very straightforward.

Using Dump Backup and Restore Linux OS

2010-02-17T01:32:00.000-08:00

dump and restore
The dump tool works by making a copy of an entire file system. The restore tool can then
take this copy and pull any and all files from it.

To support incremental backups, dump uses the concept of dump levels. A dump level of 0 means a full backup. Any dump level above 0 is an incremental relative to the last time a dump with a lower dump level occurred. For example, a dump level of 1 covers all the changes to the file system since the last level 0 dump, a dump level of 2 covers all of the changes to the file system since the last level 1 dump, and so on—all the way through dump level 9. Consider a case in which you have three dumps: the first is a level 0, the second is a level 1, and the third is also a level 1. The first dump is, of course, a full backup. The second dump (level 1) contains all the changes made since the first dump. The third dump (also a level 1) also has all the changes.

The dump utility stores all the information about its dumps in the /etc/dumpdates file.
This file lists each backed-up file system, when it was backed up, and at what dump level.
Given this information, you can determine which tape to use for a restore. For example, if you
perform level 0 dumps on Monday, level 1 incrementals on Tuesday and Wednesday, and then
level 2 incrementals on Thursday and Friday, a file that was last modified on Tuesday but got
accidentally erased on Friday can be restored from Tuesday night’s incremental backup.
A file that was last modified during the preceding week will be on Monday’s level 0 tape.

Using dump
The dump tool is a command-line utility. It takes many parameters, but the most relevant are
as shown in Table 21-2.
For example, here is the command to perform a level 0 dump to /dev/st0 of the /dev/hda1
file system:

[root@scribe /root]# dump -0 -f /dev/st0 /dev/hda1

dump Parameter Description
– n Specifies the dump level, where n is a number between 0 and 9. For
example, –0 would perform a full backup.

–b blocksize Sets the dump block size to blocksize, which is measured in kilobytes. If you
are backing up many large files, using a larger block size will increase
performance. You may need to carefully adjust this to match the capabilities
of your tape system.

–B count Specifies a number ( count) of records per tape to be dumped. If there is
more data to dump than there is tape space, dump will prompt you to insert
a new tape.

–f filename Specifies a location ( filename) for the resulting dump file. You can make the
dump file a normal file that resides on another file system, or you can write
the dump file to the tape device. The SCSI tape device is /dev/st0.

–u Updates the /etc/dumpdates file after a successful dump.

–d density Specifies the density of the tape in bits per inch.

–s size Specifies the size of the tape in feet.

–a Bypasses all tape-length calculations and writes until an end-of-media signal
is returned. This works best for most modern tape drives and is particularly
useful for appending data to existing tapes. This is the default mode.

–z or –j Compresses each data block. The –z parameter uses zlib compression, while

–j uses bzlib. Either option can be immediately followed with a number, if
you want to specify the compression level, or white space, if you want to
accept the default compression level of 2. Your tape drive must be able to
support variable-length blocks to be able to use this feature. If your tape
system has hardware compression built in, don’t use both the hardware
compression and this option together, or your files will likely increase in size.

Using dump to Back Up an Entire System
The dump utility works by making an
archive of one file system. If your entire system comprises multiple file systems, you need to
run dump for every file system. Since dump creates its output as a single, large file, you can
store multiple dumps to a single tape by using a nonrewinding tape device.
Assuming we’re backing up to a SCSI tape device, /dev/nst0, we must first decide which
file systems we’re backing up. This information is in the /etc/fstab file. Obviously, we don’t
want to back up files such as /dev/cdrom, so we skip those. Depending on our data, we may or
may not want to back up certain partitions (such as swap and /tmp).

Let’s assume this leaves us with /dev/hda1, /dev/hda3, /dev/hda5, and /dev/hda6. To
back up these to /dev/nst0, compressing them along the way, we would issue the following
series of commands:
[root@scribe /root]# mt -f /dev/nst0 rewind
[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda1
[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda3
[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda5
[root@scribe /root]# dump -0uz -f /dev/nst0 /dev/hda6
[root@scribe /root]# mt -f /dev/nst0 rewind
[root@scribe /root]# mt -f /dev/nst0 eject

Assembly Language Programming with Linux H33T

2010-02-08T11:10:00.000-08:00

Title........: Assembly Language Step-by-Step - Programming with Linux, 3rd Edition

Author.......: Jeff Duntemann

Pages........: 648

Publisher....: Wiley; 3 edition (October 5, 2009)

Language.....: English

Format.......: PDF

DOWNLOAD TORRENT

The eagerly anticipated new edition of the bestselling introduction to x86 assembly language

The long-awaited third edition of this bestselling introduction to assembly language has been completely rewritten to focus on 32-bit protected-mode Linux and the free NASM assembler. Assembly is the fundamental language bridging human ideas and the pure silicon hearts of computers, and popular author Jeff Dunteman retains his distinctive lighthearted style as he presents a step-by-step approach to this difficult technical discipline.

He starts at the very beginning, explaining the basic ideas of programmable computing, the binary and hexadecimal number systems, the Intel x86 computer architecture, and the process of software development under Linux. From that foundation he systematically treats the x86 instruction set, memory addressing, procedures, macros, and interface to the C-language code libraries upon which Linux itself is built.

Serves as an ideal introduction to x86 computing concepts, as demonstrated by the only language directly understood by the CPU itself

Uses an approachable, conversational style that assumes no prior experience in programming of any kind

Presents x86 architecture and assembly concepts through a cumulative tutorial approach that is ideal for self-paced instruction

Focuses entirely on free, open-source software, including Ubuntu Linux, the NASM assembler, the Kate editor, and the Gdb/Insight debugger.

Includes an x86 instruction set reference for the most common machine instructions, specifically tailored for use by programming beginners

Fville hack tool for FREE - 2010 window-linux

2010-01-27T14:24:00.000-08:00

Configuring Disk Quota in Linux

2010-01-12T03:19:00.000-08:00

Configuring Quota Settings
Creating, modifying, and removing quotas on either a per-user or per-group basis is done via
the edquota command. In this section, you’ll look at the usage of this command and run through
some examples as well. First, some terminology:

● Soft Limit This requested limit is placed on a user or group. If the user’s account exceeds
the soft limit, a grace period can be imposed as to how long the account can exist over the
soft limit. During this time phase, users can be warned that their accounts are over the limit.

● Hard Limit This limit is imposed by the operating system and cannot be overrun.
Any attempts to write data beyond the hard limit are denied.

● Grace Period (Time Limit) When a user’s account exceeds the soft limit, a clock starts
tracking. After the grace period expires, the user cannot access the account. The length of
this grace period should depend on the environment. A common value is one week. To
keep the account from being disabled, the user needs to remove or compress files until his
or her disk consumption falls below the soft limit

Bind 9 Fedore Setup DNS Server for Squid Cashing

2010-01-10T06:56:00.000-08:00

This is Sample Configuration for file DNS Server Configuration for
Fedora and other linux flavors which use Bind9.

1. Configure listen port (as in File)
2. Configure Allow Query (as in File)
2. Configure Forwarders (as in file)

you can also just copy and past this script in your Named.conf file
and change as per your requirement

//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named(8) DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
options {
listen-on port 53 { 127.0.0.1; 192.168.0.254; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
allow-query { localhost; 192.168.0.0/22; };
recursion yes;
forwarders { 210.2.181.6; 210.2.181.7; 4.2.2.4; };
};

logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};

zone "." IN {
type hint;
file "named.ca";
};

include "/etc/named.rfc1912.zones";

Transperent Proxy in Squid 2.6 and Squid 3

2010-01-08T03:14:00.000-08:00

This is very Simple Configuration for configure Squid 2.6 or Squid 3.0
act as a Transparent. if you are old user of Squid and linux then this is very simple
configuration all the squid configuration same.
when you configure just type transparent after port as under:-

http_port 3128 transparent

Further Setting and tracks of squid i will write in my next blog
Thanks.

Further Help contact with us
LinuxMall Team
Pakistan
092-321-8466323

squid.conf sample file of fedora

2010-01-04T03:21:00.000-08:00

# WELCOME TO SQUID 2
# ------------------
#
# This is the default Squid configuration file. You may wish
# to look at the Squid home page (http://www.squid-cache.org/)
# for the FAQ and other documentation.
#
# The default Squid config file shows what the defaults for
# various options happen to be. If you don't need to change the
# default, you shouldn't uncomment the line. Doing so may cause
# run-time problems. In some cases "none" refers to no default
# setting at all, while in other cases it refers to a valid
# option - the comments for that keyword indicate if this is the
# case.
#
# NETWORK OPTIONS
# -----------------------------------------------------------------------------

# TAG: http_port
# Usage: port
# hostname:port
# 1.2.3.4:port
#
# The socket addresses where Squid will listen for HTTP client
# requests. You may specify multiple socket addresses.
# There are three forms: port alone, hostname with port, and
# IP address with port. If you specify a hostname or IP
# address, Squid binds the socket to that specific
# address. This replaces the old 'tcp_incoming_address'
# option. Most likely, you do not need to bind to a specific
# address, so you can use the port number alone.
#
# The default port number is 3128.
#
# If you are running Squid in accelerator mode, you
# probably want to listen on port 80 also, or instead.
#
# The -a command line option will override the *first* port
# number listed here. That option will NOT override an IP
# address, however.
#
# You may specify multiple socket addresses on multiple lines.
#
# If you run Squid on a dual-homed machine with an internal
# and an external interface we recommend you to specify the
# internal address:port in http_port. This way Squid will only be
# visible on the internal address.
#
#Default:
http_port 8080

# TAG: https_port
# Usage: [ip:]port cert=certificate.pem [key=key.pem] [options...]
#
# The socket address where Squid will listen for HTTPS client
# requests.
#
# This is really only useful for situations where you are running
# squid in accelerator mode and you want to do the SSL work at the
# accelerator level.
#
# You may specify multiple socket addresses on multiple lines,
# each with their own SSL certificate and/or options.
#
# Options:
#
# cert= Path to SSL certificate (PEM format)
#
# key= Path to SSL private key file (PEM format)
# if not specified, the certificate file is
# assumed to be a combined certificate and
# key file
#
# version= The version of SSL/TLS supported
# 1 automatic (default)
# 2 SSLv2 only
# 3 SSLv3 only
# 4 TLSv1 only
#
# cipher= Colon separated list of supported ciphers
#
# options= Various SSL engine options. The most important
# being:
# NO_SSLv2 Disallow the use of SSLv2
# NO_SSLv3 Disallow the use of SSLv3
# NO_TLSv1 Disallow the use of TLSv1
# See src/ssl_support.c or OpenSSL documentation
# for a more complete list.
#
#Default:
# none

# TAG: ssl_unclean_shutdown
# Some browsers (especially MSIE) bugs out on SSL shutdown
# messages.
#
#Default:
# ssl_unclean_shutdown off

# TAG: icp_port
# The port number where Squid sends and receives ICP queries to
# and from neighbor caches. Default is 3130. To disable use
# "0". May be overridden with -u on the command line.
#
#Default:
# icp_port 3130

# TAG: htcp_port
# Note: This option is only available if Squid is rebuilt with the
# --enable-htcp option
#
# The port number where Squid sends and receives HTCP queries to
# and from neighbor caches. Default is 4827. To disable use
# "0".
#
#Default:
# htcp_port 4827

# TAG: mcast_groups
# This tag specifies a list of multicast groups which your server
# should join to receive multicasted ICP queries.
#
# NOTE! Be very careful what you put here! Be sure you
# understand the difference between an ICP _query_ and an ICP
# _reply_. This option is to be set only if you want to RECEIVE
# multicast queries. Do NOT set this option to SEND multicast
# ICP (use cache_peer for that). ICP replies are always sent via
# unicast, so this option does not affect whether or not you will
# receive replies from multicast group members.
#
# You must be very careful to NOT use a multicast address which
# is already in use by another group of caches.
#
# If you are unsure about multicast, please read the Multicast
# chapter in the Squid FAQ (http://www.squid-cache.org/FAQ/).
#
# Usage: mcast_groups 239.128.16.128 224.0.1.20
#
# By default, Squid doesn't listen on any multicast groups.
#
#Default:
# none

# TAG: udp_incoming_address
# TAG: udp_outgoing_address
# udp_incoming_address is used for the ICP socket receiving packets
# from other caches.
# udp_outgoing_address is used for ICP packets sent out to other
# caches.
#
# The default behavior is to not bind to any specific address.
#
# A udp_incoming_address value of 0.0.0.0 indicates Squid
# should listen for UDP messages on all available interfaces.
#
# If udp_outgoing_address is set to 255.255.255.255 (the default)
# it will use the same socket as udp_incoming_address. Only
# change this if you want to have ICP queries sent using another
# address than where this Squid listens for ICP queries from other
# caches.
#
# NOTE, udp_incoming_address and udp_outgoing_address can not
# have the same value since they both use port 3130.
#
#Default:
# udp_incoming_address 0.0.0.0
# udp_outgoing_address 255.255.255.255

# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM
# -----------------------------------------------------------------------------

# TAG: cache_peer
# To specify other caches in a hierarchy, use the format:
#
# cache_peer hostname type http_port icp_port
#
# For example,
#
# # proxy icp
# # hostname type port port options
# # -------------------- -------- ----- ----- -----------
cache_peer 192.168.0.253 parent 3128 3130 round-robin
cache_peer 192.168.0.10 parent 8080 0 round-robin
# cache_peer sib1.foo.net sibling 3128 3130 [proxy-only]
# cache_peer sib2.foo.net sibling 3128 3130 [proxy-only]
#
# type: either 'parent', 'sibling', or 'multicast'.
#
# proxy_port: The port number where the cache listens for proxy
# requests.
#
# icp_port: Used for querying neighbor caches about
# objects. To have a non-ICP neighbor
# specify '7' for the ICP port and make sure the
# neighbor machine has the UDP echo port
# enabled in its /etc/inetd.conf file.
#
# options: proxy-only
# weight=n
# ttl=n
# no-query
# default
# round-robin
# multicast-responder
# closest-only
# no-digest
# no-netdb-exchange
# no-delay
# login=user:password | PASS | *:password
# connect-timeout=nn
# digest-url=url
# allow-miss
# max-conn
# htcp
# carp-load-factor
#
# use 'proxy-only' to specify objects fetched
# from this cache should not be saved locally.
#
# use 'weight=n' to specify a weighted parent.
# The weight must be an integer. The default weight
# is 1, larger weights are favored more.
#
# use 'ttl=n' to specify a IP multicast TTL to use
# when sending an ICP queries to this address.
# Only useful when sending to a multicast group.
# Because we don't accept ICP replies from random
# hosts, you must configure other group members as
# peers with the 'multicast-responder' option below.
#
# use 'no-query' to NOT send ICP queries to this
# neighbor.
#
# use 'default' if this is a parent cache which can
# be used as a "last-resort." You should probably
# only use 'default' in situations where you cannot
# use ICP with your parent cache(s).
#
# use 'round-robin' to define a set of parents which
# should be used in a round-robin fashion in the
# absence of any ICP queries.
#
# 'multicast-responder' indicates the named peer
# is a member of a multicast group. ICP queries will
# not be sent directly to the peer, but ICP replies
# will be accepted from it.
#
# 'closest-only' indicates that, for ICP_OP_MISS
# replies, we'll only forward CLOSEST_PARENT_MISSes
# and never FIRST_PARENT_MISSes.
#
# use 'no-digest' to NOT request cache digests from
# this neighbor.
#
# 'no-netdb-exchange' disables requesting ICMP
# RTT database (NetDB) from the neighbor.
#
# use 'no-delay' to prevent access to this neighbor
# from influencing the delay pools.
#
# use 'login=user:password' if this is a personal/workgroup
# proxy and your parent requires proxy authentication.
# Note: The string can include URL escapes (i.e. %20 for
# spaces). This also means % must be written as %%.
#
# use 'login=PASS' if users must authenticate against
# the upstream proxy. This will pass the users credentials
# as they are to the peer proxy. This only works for the
# Basic HTTP authentication scheme. Note: To combine this
# with proxy_auth both proxies must share the same user
# database as HTTP only allows for one proxy login.
# Also be warned this will expose your users proxy
# password to the peer. USE WITH CAUTION
#
# use 'login=*:password' to pass the username to the
# upstream cache, but with a fixed password. This is meant
# to be used when the peer is in another administrative
# domain, but it is still needed to identify each user.
# The star can optionally be followed by some extra
# information which is added to the username. This can
# be used to identify this proxy to the peer, similar to
# the login=username:password option above.
#
# use 'connect-timeout=nn' to specify a peer
# specific connect timeout (also see the
# peer_connect_timeout directive)
#
# use 'digest-url=url' to tell Squid to fetch the cache
# digest (if digests are enabled) for this host from
# the specified URL rather than the Squid default
# location.
#
# use 'allow-miss' to disable Squid's use of only-if-cached
# when forwarding requests to siblings. This is primarily
# useful when icp_hit_stale is used by the sibling. To
# extensive use of this option may result in forwarding
# loops, and you should avoid having two-way peerings
# with this option. (for example to deny peer usage on
# requests from peer by denying cache_peer_access if the
# source is a peer)
#
# use 'max-conn' to limit the amount of connections Squid
# may open to this peer.
#
# use 'htcp' to send HTCP, instead of ICP, queries
# to the neighbor. You probably also want to
# set the "icp port" to 4827 instead of 3130.
#
# use 'carp-load-factor=f' to define a parent
# cache as one participating in a CARP array.
# The 'f' values for all CARP parents must add
# up to 1.0.
#
#
# NOTE: non-ICP/HTCP neighbors must be specified as 'parent'.
#
#Default:
# none

# TAG: cache_peer_domain
# Use to limit the domains for which a neighbor cache will be
# queried. Usage:
#
# cache_peer_domain cache-host domain [domain ...]
# cache_peer_domain cache-host !domain
#
# For example, specifying
#
# cache_peer_domain parent.foo.net .edu
#
# has the effect such that UDP query packets are sent to
# 'bigserver' only when the requested object exists on a
# server in the .edu domain. Prefixing the domainname
# with '!' means the cache will be queried for objects
# NOT in that domain.
#
# NOTE: * Any number of domains may be given for a cache-host,
# either on the same or separate lines.
# * When multiple domains are given for a particular
# cache-host, the first matched domain is applied.
# * Cache hosts with no domain restrictions are queried
# for all requests.
# * There are no defaults.
# * There is also a 'cache_peer_access' tag in the ACL
# section.
#
#Default:
# none

# TAG: neighbor_type_domain
# usage: neighbor_type_domain neighbor parent|sibling domain domain ...
#
# Modifying the neighbor type for specific domains is now
# possible. You can treat some domains differently than the the
# default neighbor type specified on the 'cache_peer' line.
# Normally it should only be necessary to list domains which
# should be treated differently because the default neighbor type
# applies for hostnames which do not match domains listed here.
#
#EXAMPLE:
# cache_peer parent cache.foo.org 3128 3130
# neighbor_type_domain cache.foo.org sibling .com .net
# neighbor_type_domain cache.foo.org sibling .au .de
#
#Default:
# none

# TAG: icp_query_timeout (msec)
# Normally Squid will automatically determine an optimal ICP
# query timeout value based on the round-trip-time of recent ICP
# queries. If you want to override the value determined by
# Squid, set this 'icp_query_timeout' to a non-zero value. This
# value is specified in MILLISECONDS, so, to use a 2-second
# timeout (the old default), you would write:
#
# icp_query_timeout 2000
#
#Default:
# icp_query_timeout 0

# TAG: maximum_icp_query_timeout (msec)
# Normally the ICP query timeout is determined dynamically. But
# sometimes it can lead to very large values (say 5 seconds).
# Use this option to put an upper limit on the dynamic timeout
# value. Do NOT use this option to always use a fixed (instead
# of a dynamic) timeout value. To set a fixed timeout see the
# 'icp_query_timeout' directive.
#
#Default:
# maximum_icp_query_timeout 2000

# TAG: mcast_icp_query_timeout (msec)
# For Multicast peers, Squid regularly sends out ICP "probes" to
# count how many other peers are listening on the given multicast
# address. This value specifies how long Squid should wait to
# count all the replies. The default is 2000 msec, or 2
# seconds.
#
#Default:
# mcast_icp_query_timeout 2000

# TAG: dead_peer_timeout (seconds)
# This controls how long Squid waits to declare a peer cache
# as "dead." If there are no ICP replies received in this
# amount of time, Squid will declare the peer dead and not
# expect to receive any further ICP replies. However, it
# continues to send ICP queries, and will mark the peer as
# alive upon receipt of the first subsequent ICP reply.
#
# This timeout also affects when Squid expects to receive ICP
# replies from peers. If more than 'dead_peer' seconds have
# passed since the last ICP reply was received, Squid will not
# expect to receive an ICP reply on the next query. Thus, if
# your time between requests is greater than this timeout, you
# will see a lot of requests sent DIRECT to origin servers
# instead of to your parents.
#
#Default:
# dead_peer_timeout 10 seconds

# TAG: hierarchy_stoplist
# A list of words which, if found in a URL, cause the object to
# be handled directly by this cache. In other words, use this
# to not query neighbor caches for certain objects. You may
# list this option multiple times. Note: never_direct overrides
# this option.
#We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?

# TAG: no_cache
# A list of ACL elements which, if matched, cause the request to
# not be satisfied from the cache and the reply to not be cached.
# In other words, use this to force certain objects to never be cached.
#
# You must use the word 'DENY' to indicate the ACL names which should
# NOT be cached.
#
#We recommend you to use the following two lines.
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY

# OPTIONS WHICH AFFECT THE CACHE SIZE
# -----------------------------------------------------------------------------

# TAG: cache_mem (bytes)
# NOTE: THIS PARAMETER DOES NOT SPECIFY THE MAXIMUM PROCESS SIZE.
# IT ONLY PLACES A LIMIT ON HOW MUCH ADDITIONAL MEMORY SQUID WILL
# USE AS A MEMORY CACHE OF OBJECTS. SQUID USES MEMORY FOR OTHER
# THINGS AS WELL. SEE THE SQUID FAQ SECTION 8 FOR DETAILS.
#
# 'cache_mem' specifies the ideal amount of memory to be used
# for:
# * In-Transit objects
# * Hot Objects
# * Negative-Cached objects
#
# Data for these objects are stored in 4 KB blocks. This
# parameter specifies the ideal upper limit on the total size of
# 4 KB blocks allocated. In-Transit objects take the highest
# priority.
#
# In-transit objects have priority over the others. When
# additional space is needed for incoming data, negative-cached
# and hot objects will be released. In other words, the
# negative-cached and hot objects will fill up any unused space
# not needed for in-transit objects.
#
# If circumstances require, this limit will be exceeded.
# Specifically, if your incoming request rate requires more than
# 'cache_mem' of memory to hold in-transit objects, Squid will
# exceed this limit to satisfy the new requests. When the load
# decreases, blocks will be freed until the high-water mark is
# reached. Thereafter, blocks will be used to store hot
# objects.
#
#Default:
# cache_mem 128 MB

# TAG: cache_swap_low (percent, 0-100)
# TAG: cache_swap_high (percent, 0-100)
#
# The low- and high-water marks for cache object replacement.
# Replacement begins when the swap (disk) usage is above the
# low-water mark and attempts to maintain utilization near the
# low-water mark. As swap utilization gets close to high-water
# mark object eviction becomes more aggressive. If utilization is
# close to the low-water mark less replacement is done each time.
#
# Defaults are 90% and 95%. If you have a large cache, 5% could be
# hundreds of MB. If this is the case you may wish to set these
# numbers closer together.
#
#Default:
# cache_swap_low 90
# cache_swap_high 95

# TAG: maximum_object_size (bytes)
# Objects larger than this size will NOT be saved on disk. The
# value is specified in kilobytes, and the default is 4MB. If
# you wish to get a high BYTES hit ratio, you should probably
# increase this (one 32 MB object hit counts for 3200 10KB
# hits). If you wish to increase speed more than your want to
# save bandwidth you should leave this low.
#
# NOTE: if using the LFUDA replacement policy you should increase
# this value to maximize the byte hit rate improvement of LFUDA!
# See replacement_policy below for a discussion of this policy.
#
#Default:
# maximum_object_size 300 MB

# TAG: minimum_object_size (bytes)
# Objects smaller than this size will NOT be saved on disk. The
# value is specified in kilobytes, and the default is 0 KB, which
# means there is no minimum.
#
#Default:
# minimum_object_size 0 KB

# TAG: maximum_object_size_in_memory (bytes)
# Objects greater than this size will not be attempted to kept in
# the memory cache. This should be set high enough to keep objects
# accessed frequently in memory to improve performance whilst low
# enough to keep larger objects from hoarding cache_mem .
#
#Default:
# maximum_object_size_in_memory 8 KB

# TAG: ipcache_size (number of entries)
# TAG: ipcache_low (percent)
# TAG: ipcache_high (percent)
# The size, low-, and high-water marks for the IP cache.
#
#Default:
# ipcache_size 1024
# ipcache_low 90
# ipcache_high 95

# TAG: fqdncache_size (number of entries)
# Maximum number of FQDN cache entries.
#
#Default:
# fqdncache_size 1024

# TAG: cache_replacement_policy
# The cache replacement policy parameter determines which
# objects are evicted (replaced) when disk space is needed.
#
# lru : Squid's original list based LRU policy
# heap GDSF : Greedy-Dual Size Frequency
# heap LFUDA: Least Frequently Used with Dynamic Aging
# heap LRU : LRU policy implemented using a heap
#
# Applies to any cache_dir lines listed below this.
#
# The LRU policies keeps recently referenced objects.
#
# The heap GDSF policy optimizes object hit rate by keeping smaller
# popular objects in cache so it has a better chance of getting a
# hit. It achieves a lower byte hit rate than LFUDA though since
# it evicts larger (possibly popular) objects.
#
# The heap LFUDA policy keeps popular objects in cache regardless of
# their size and thus optimizes byte hit rate at the expense of
# hit rate since one large, popular object will prevent many
# smaller, slightly less popular objects from being cached.
#
# Both policies utilize a dynamic aging mechanism that prevents
# cache pollution that can otherwise occur with frequency-based
# replacement policies.
#
# NOTE: if using the LFUDA replacement policy you should increase
# the value of maximum_object_size above its default of 4096 KB to
# to maximize the potential byte hit rate improvement of LFUDA.
#
# For more information about the GDSF and LFUDA cache replacement
# policies see http://www.hpl.hp.com/techreports/1999/HPL-1999-69.html
# and http://fog.hpl.external.hp.com/techreports/98/HPL-98-173.html.
#
#Default:
# cache_replacement_policy lru

# TAG: memory_replacement_policy
# The memory replacement policy parameter determines which
# objects are purged from memory when memory space is needed.
#
# See cache_replacement_policy for details.
#
#Default:
# memory_replacement_policy lru

# LOGFILE PATHNAMES AND CACHE DIRECTORIES
# -----------------------------------------------------------------------------

# TAG: cache_dir
# Usage:
#
# cache_dir Type Directory-Name Fs-specific-data [options]
#
# You can specify multiple cache_dir lines to spread the
# cache among different disk partitions.
#
# Type specifies the kind of storage system to use. Only "ufs"
# is built by default. To enable any of the other storage systems
# see the --enable-storeio configure option.
#
# 'Directory' is a top-level directory where cache swap
# files will be stored. If you want to use an entire disk
# for caching, this can be the mount-point directory.
# The directory must exist and be writable by the Squid
# process. Squid will NOT create this directory for you.
#
# The ufs store type:
#
# "ufs" is the old well-known Squid storage format that has always
# been there.
#
# cache_dir ufs Directory-Name Mbytes L1 L2 [options]
#
# 'Mbytes' is the amount of disk space (MB) to use under this
# directory. The default is 100 MB. Change this to suit your
# configuration. Do NOT put the size of your disk drive here.
# Instead, if you want Squid to use the entire disk drive,
# subtract 20% and use that value.
#
# 'Level-1' is the number of first-level subdirectories which
# will be created under the 'Directory'. The default is 16.
#
# 'Level-2' is the number of second-level subdirectories which
# will be created under each first-level directory. The default
# is 256.
#
# The aufs store type:
#
# "aufs" uses the same storage format as "ufs", utilizing
# POSIX-threads to avoid blocking the main Squid process on
# disk-I/O. This was formerly known in Squid as async-io.
#
# cache_dir aufs Directory-Name Mbytes L1 L2 [options]
#
# see argument descriptions under ufs above
#
# The diskd store type:
#
# "diskd" uses the same storage format as "ufs", utilizing a
# separate process to avoid blocking the main Squid process on
# disk-I/O.
#
# cache_dir diskd Directory-Name Mbytes L1 L2 [options] [Q1=n] [Q2=n]
#
# see argument descriptions under ufs above
#
# Q1 specifies the number of unacknowledged I/O requests when Squid
# stops opening new files. If this many messages are in the queues,
# Squid won't open new files. Default is 64
#
# Q2 specifies the number of unacknowledged messages when Squid
# starts blocking. If this many messages are in the queues,
# Squid blocks until it receives some replies. Default is 72
#
# When Q1 < Q2 (the default), the cache directory is optimized
# for lower response time at the expense of a decrease in hit
# ratio. If Q1 > Q2, the cache directory is optimized for
# higher hit ratio at the expense of an increase in response
# time.
#
# The coss store type:
#
# block-size=n defines the "block size" for COSS cache_dir's.
# Squid uses file numbers as block numbers. Since file numbers
# are limited to 24 bits, the block size determines the maximum
# size of the COSS partition. The default is 512 bytes, which
# leads to a maximum cache_dir size of 512<<24, or 8 GB. Note
# you should not change the coss block size after Squid
# has written some objects to the cache_dir.
#
# Common options:
#
# read-only, this cache_dir is read only.
#
# max-size=n, refers to the max object size this storedir supports.
# It is used to initially choose the storedir to dump the object.
# Note: To make optimal use of the max-size limits you should order
# the cache_dir lines with the smallest max-size value first and the
# ones with no max-size specification last.
#
# Note that for coss, max-size must be less than COSS_MEMBUF_SZ
# (hard coded at 1 MB).
#
#Default:
cache_dir ufs /var/spool/squid 42000 16 256

# TAG: cache_access_log
# Logs the client request activity. Contains an entry for
# every HTTP and ICP queries received. To disable, enter "none".
#
#Default:
# cache_access_log /var/log/squid/access.log

# TAG: cache_log
# Cache logging file. This is where general information about
# your cache's behavior goes. You can increase the amount of data
# logged to this file with the "debug_options" tag below.
#
#Default:
# cache_log /var/log/squid/cache.log

# TAG: cache_store_log
# Logs the activities of the storage manager. Shows which
# objects are ejected from the cache, and which objects are
# saved and for how long. To disable, enter "none". There are
# not really utilities to analyze this data, so you can safely
# disable it.
#
#Default:
# cache_store_log /var/log/squid/store.log

# TAG: cache_swap_log
# Location for the cache "swap.state" file. This log file holds
# the metadata of objects saved on disk. It is used to rebuild
# the cache during startup. Normally this file resides in each
# 'cache_dir' directory, but you may specify an alternate
# pathname here. Note you must give a full filename, not just
# a directory. Since this is the index for the whole object
# list you CANNOT periodically rotate it!
#
# If %s can be used in the file name it will be replaced with a
# a representation of the cache_dir name where each / is replaced
# with '.'. This is needed to allow adding/removing cache_dir
# lines when cache_swap_log is being used.
#
# If have more than one 'cache_dir', and %s is not used in the name
# these swap logs will have names such as:
#
# cache_swap_log.00
# cache_swap_log.01
# cache_swap_log.02
#
# The numbered extension (which is added automatically)
# corresponds to the order of the 'cache_dir' lines in this
# configuration file. If you change the order of the 'cache_dir'
# lines in this file, these log files will NOT correspond to
# the correct 'cache_dir' entry (unless you manually rename
# them). We recommend you do NOT use this option. It is
# better to keep these log files in each 'cache_dir' directory.
#
#Default:
# none

# TAG: emulate_httpd_log on|off
# The Cache can emulate the log file format which many 'httpd'
# programs use. To disable/enable this emulation, set
# emulate_httpd_log to 'off' or 'on'. The default
# is to use the native log format since it includes useful
# information Squid-specific log analyzers use.
#
#Default:
# emulate_httpd_log off

# TAG: log_ip_on_direct on|off
# Log the destination IP address in the hierarchy log tag when going
# direct. Earlier Squid versions logged the hostname here. If you
# prefer the old way set this to off.
#
#Default:
# log_ip_on_direct on

# TAG: mime_table
# Pathname to Squid's MIME table. You shouldn't need to change
# this, but the default file contains examples and formatting
# information if you do.
#
#Default:
# mime_table /etc/squid/mime.conf

# TAG: log_mime_hdrs on|off
# The Cache can record both the request and the response MIME
# headers for each HTTP transaction. The headers are encoded
# safely and will appear as two bracketed fields at the end of
# the access log (for either the native or httpd-emulated log
# formats). To enable this logging set log_mime_hdrs to 'on'.
#
#Default:
# log_mime_hdrs off

# TAG: useragent_log
# Squid will write the User-Agent field from HTTP requests
# to the filename specified here. By default useragent_log
# is disabled.
#
#Default:
# none

# TAG: referer_log
# Squid will write the Referer field from HTTP requests to the
# filename specified here. By default referer_log is disabled.
#
#Default:
# none

# TAG: pid_filename
# A filename to write the process-id to. To disable, enter "none".
#
#Default:
# pid_filename /var/run/squid.pid

# TAG: debug_options
# Logging options are set as section,level where each source file
# is assigned a unique section. Lower levels result in less
# output, Full debugging (level 9) can result in a very large
# log file, so be careful. The magic word "ALL" sets debugging
# levels for all sections. We recommend normally running with
# "ALL,1".
#
#Default:
# debug_options ALL,1

# TAG: log_fqdn on|off
# Turn this on if you wish to log fully qualified domain names
# in the access.log. To do this Squid does a DNS lookup of all
# IP's connecting to it. This can (in some situations) increase
# latency, which makes your cache seem slower for interactive
# browsing.
#
#Default:
# log_fqdn off

# TAG: client_netmask
# A netmask for client addresses in logfiles and cachemgr output.
# Change this to protect the privacy of your cache clients.
# A netmask of 255.255.255.0 will log all IP's in that range with
# the last digit set to '0'.
#
#Default:
# client_netmask 255.255.255.255

# OPTIONS FOR EXTERNAL SUPPORT PROGRAMS
# -----------------------------------------------------------------------------

# TAG: ftp_user
# If you want the anonymous login password to be more informative
# (and enable the use of picky ftp servers), set this to something
# reasonable for your domain, like wwwuser@somewhere.net
#
# The reason why this is domainless by default is the
# request can be made on the behalf of a user in any domain,
# depending on how the cache is used.
# Some ftp server also validate the email address is valid
# (for example perl.com).
#
#Default:
# ftp_user Squid@

# TAG: ftp_list_width
# Sets the width of ftp listings. This should be set to fit in
# the width of a standard browser. Setting this too small
# can cut off long filenames when browsing ftp sites.
#
#Default:
# ftp_list_width 32

# TAG: ftp_passive
# If your firewall does not allow Squid to use passive
# connections, turn off this option.
#
#Default:
# ftp_passive on

# TAG: ftp_sanitycheck
# For security and data integrity reasons Squid by default performs
# sanity checks of the addresses of FTP data connections ensure the
# data connection is to the requested server. If you need to allow
# FTP connections to servers using another IP address for the data
# connection turn this off.
#
#Default:
# ftp_sanitycheck on

# TAG: ftp_telnet_protocol
# The FTP protocol is officially defined to use the telnet protocol
# as transport channel for the control connection. However, many
# implementations are broken and does not respect this aspect of
# the FTP protocol.
#
# If you have trouble accessing files with ASCII code 255 in the
# path or similar problems involving this ASCII code you can
# try setting this directive to off. If that helps, report to the
# operator of the FTP server in question that their FTP server
# is broken and does not follow the FTP standard.
#
#Default:
# ftp_telnet_protocol on

# TAG: cache_dns_program
# Note: This option is only available if Squid is rebuilt with the
# --disable-internal-dns option
#
# Specify the location of the executable for dnslookup process.
#
#Default:
# cache_dns_program /usr/lib/squid/dnsserver

# TAG: dns_children
# Note: This option is only available if Squid is rebuilt with the
# --disable-internal-dns option
#
# The number of processes spawn to service DNS name lookups.
# For heavily loaded caches on large servers, you should
# probably increase this value to at least 10. The maximum
# is 32. The default is 5.
#
# You must have at least one dnsserver process.
#
#Default:
# dns_children 5

# TAG: dns_retransmit_interval
# Initial retransmit interval for DNS queries. The interval is
# doubled each time all configured DNS servers have been tried.
#
#
#Default:
# dns_retransmit_interval 5 seconds

# TAG: dns_timeout
# DNS Query timeout. If no response is received to a DNS query
# within this time all DNS servers for the queried domain
# are assumed to be unavailable.
#
#Default:
# dns_timeout 2 minutes

# TAG: dns_defnames on|off
# Note: This option is only available if Squid is rebuilt with the
# --disable-internal-dns option
#
# Normally the 'dnsserver' disables the RES_DEFNAMES resolver
# option (see res_init(3)). This prevents caches in a hierarchy
# from interpreting single-component hostnames locally. To allow
# dnsserver to handle single-component names, enable this
# option.
#
#Default:
# dns_defnames off

# TAG: dns_nameservers
# Use this if you want to specify a list of DNS name servers
# (IP addresses) to use instead of those given in your
# /etc/resolv.conf file.
# On Windows platforms, if no value is specified here or in
# the /etc/resolv.conf file, the list of DNS name servers are
# taken from the Windows registry, both static and dynamic DHCP
# configurations are supported.
#
# Example: dns_nameservers 10.0.0.1 192.172.0.4
#
#Default:
# none

# TAG: hosts_file
# Location of the host-local IP name-address associations
# database. Most Operating Systems have such a file: under
# Un*X it's by default in /etc/hosts. MS-Windows NT/2000 places
# it in %SystemRoot%(by default
# c:\winnt)\system32\drivers\etc\hosts, while Windows 9x/ME
# places it in %windir%(usually c:\windows)\hosts
#
# The file contains newline-separated definitions, in the
# form ip_address_in_dotted_form name [name ...] names are
# whitespace-separated. lines beginning with an hash (#)
# character are comments.
#
# The file is checked at startup and upon configuration. If
# set to 'none', it won't be checked. If append_domain is
# used, that domain will be added to domain-local (i.e. not
# containing any dot character) host definitions.
#
#Default:
# hosts_file /etc/hosts

# TAG: diskd_program
# Specify the location of the diskd executable.
# Note that this is only useful if you have compiled in
# diskd as one of the store io modules.
#
#Default:
# diskd_program /usr/lib/squid/diskd

# TAG: unlinkd_program
# Specify the location of the executable for file deletion process.
#
#Default:
# unlinkd_program /usr/lib/squid/unlinkd

# TAG: pinger_program
# Note: This option is only available if Squid is rebuilt with the
# --enable-icmp option
#
# Specify the location of the executable for the pinger process.
#
#Default:
# pinger_program /usr/lib/squid/pinger

# TAG: redirect_program
# Specify the location of the executable for the URL redirector.
# Since they can perform almost any function there isn't one included.
# See the FAQ (section 15) for information on how to write one.
# By default, a redirector is not used.
#
#Default:
# none

# TAG: redirect_children
# The number of redirector processes to spawn. If you start
# too few Squid will have to wait for them to process a backlog of
# URLs, slowing it down. If you start too many they will use RAM
# and other system resources.
#
#Default:
# redirect_children 5

# TAG: redirect_rewrites_host_header
# By default Squid rewrites any Host: header in redirected
# requests. If you are running an accelerator this may
# not be a wanted effect of a redirector.
#
#Default:
# redirect_rewrites_host_header on

# TAG: redirector_access
# If defined, this access list specifies which requests are
# sent to the redirector processes. By default all requests
# are sent.
#
#Default:
# none

# TAG: auth_param
# This is used to define parameters for the various authentication
# schemes supported by Squid.
#
# format: auth_param scheme parameter [setting]
#
# The order in which authentication schemes are presented to the client is
# dependent on the order the scheme first appears in config file. IE
# has a bug (it's not rfc 2617 compliant) in that it will use the basic
# scheme if basic is the first entry presented, even if more secure
# schemes are presented. For now use the order in the recommended
# settings section below. If other browsers have difficulties (don't
# recognize the schemes offered even if you are using basic) either
# put basic first, or disable the other schemes (by commenting out their
# program entry).
#
# Once an authentication scheme is fully configured, it can only be
# shutdown by shutting squid down and restarting. Changes can be made on
# the fly and activated with a reconfigure. I.E. You can change to a
# different helper, but not unconfigure the helper completely.
#
# Please note that while this directive defines how Squid processes
# authentication it does not automatically activate authentication.
# To use authentication you must in addition make use of ACLs based
# on login name in http_access (proxy_auth, proxy_auth_regex or
# external with %LOGIN used in the format tag). The browser will be
# challenged for authentication on the first such acl encountered
# in http_access processing and will also be re-challenged for new
# login credentials if the request is being denied by a proxy_auth
# type acl.
#
# WARNING: authentication can't be used in a transparently intercepting
# proxy as the client then thinks it is talking to an origin server and
# not the proxy. This is a limitation of bending the TCP/IP protocol to
# transparently intercepting port 80, not a limitation in Squid.
#
# === Parameters for the basic scheme follow. ===
#
# "program" cmdline
# Specify the command for the external authenticator. Such a program
# reads a line containing "username password" and replies "OK" or
# "ERR" in an endless loop. "ERR" responses may optionally be followed
# by a error description available as %m in the returned error page.
#
# By default, the basic authentication scheme is not used unless a
# program is specified.
#
# If you want to use the traditional proxy authentication, jump over to
# the helpers/basic_auth/NCSA directory and type:
# % make
# % make install
#
# Then, set this line to something like
#
# auth_param basic program /usr/libexec/ncsa_auth /usr/etc/passwd
#
# "children" numberofchildren
# The number of authenticator processes to spawn.
# If you start too few Squid will have to wait for them to process a
# backlog of usercode/password verifications, slowing it down. When
# password verifications are done via a (slow) network you are likely to
# need lots of authenticator processes.
# auth_param basic children 5
#
# "realm" realmstring
# Specifies the realm name which is to be reported to the client for
# the basic proxy authentication scheme (part of the text the user
# will see when prompted their username and password).
# auth_param basic realm Squid proxy-caching web server
#
# "credentialsttl" timetolive
# Specifies how long squid assumes an externally validated
# username:password pair is valid for - in other words how often the
# helper program is called for that user. Set this low to force
# revalidation with short lived passwords. Note that setting this high
# does not impact your susceptibility to replay attacks unless you are
# using an one-time password system (such as SecureID). If you are using
# such a system, you will be vulnerable to replay attacks unless you
# also use the max_user_ip ACL in an http_access rule.
# auth_param basic credentialsttl 2 hours
#
# "casesensitive" on|off
# Specifies if usernames are case sensitive. Most user databases are
# case insensitive allowing the same username to be spelled using both
# lower and upper case letters, but some are case sensitive. This
# makes a big difference for user_max_ip ACL processing and similar.
# auth_param basic casesensitive off
#
# === Parameters for the digest scheme follow ===
#
# "program" cmdline
# Specify the command for the external authenticator. Such a program
# reads a line containing "username":"realm" and replies with the
# appropriate H(A1) value base64 encoded or ERR if the user (or his H(A1)
# hash) does not exists. See rfc 2616 for the definition of H(A1).
# "ERR" responses may optionally be followed by a error description
# available as %m in the returned error page.
#
# By default, the digest authentication scheme is not used unless a
# program is specified.
#
# If you want to use a digest authenticator, jump over to the
# helpers/digest_auth/ directory and choose the authenticator to use.
# It it's directory type
# % make
# % make install
#
# Then, set this line to something like
#
# auth_param digest program /usr/libexec/digest_auth_pw /usr/etc/digpass
#
#
# "children" numberofchildren
# The number of authenticator processes to spawn (no default). If you
# start too few Squid will have to wait for them to process a backlog of
# H(A1) calculations, slowing it down. When the H(A1) calculations are
# done via a (slow) network you are likely to need lots of authenticator
# processes.
# auth_param digest children 5
#
# "realm" realmstring
# Specifies the realm name which is to be reported to the client for the
# digest proxy authentication scheme (part of the text the user will see
# when prompted their username and password).
# auth_param digest realm Squid proxy-caching web server
#
# "nonce_garbage_interval" timeinterval
# Specifies the interval that nonces that have been issued to clients are
# checked for validity.
# auth_param digest nonce_garbage_interval 5 minutes
#
# "nonce_max_duration" timeinterval
# Specifies the maximum length of time a given nonce will be valid for.
# auth_param digest nonce_max_duration 30 minutes
#
# "nonce_max_count" number
# Specifies the maximum number of times a given nonce can be used.
# auth_param digest nonce_max_count 50
#
# "nonce_strictness" on|off
# Determines if squid requires strict increment-by-1 behavior for nonce
# counts, or just incrementing (off - for use when useragents generate
# nonce counts that occasionally miss 1 (ie, 1,2,4,6)).
# auth_param digest nonce_strictness off
#
# "check_nonce_count" on|off
# This directive if set to off can disable the nonce count check
# completely to work around buggy digest qop implementations in certain
# mainstream browser versions. Default on to check the nonce count to
# protect from authentication replay attacks.
# auth_param digest check_nonce_count on
#
# "post_workaround" on|off
# This is a workaround to certain buggy browsers who sends an incorrect
# request digest in POST requests when reusing the same nonce as acquired
# earlier in response to a GET request.
# auth_param digest post_workaround off
#
# === NTLM scheme options follow ===
#
# "program" cmdline
# Specify the command for the external NTLM authenticator. Such a
# program participates in the NTLMSSP exchanges between Squid and the
# client and reads commands according to the Squid NTLMSSP helper
# protocol. See helpers/ntlm_auth/ for details. Recommended ntlm
# authenticator is ntlm_auth from Samba-3.X, but a number of other
# ntlm authenticators is available.
#
# By default, the ntlm authentication scheme is not used unless a
# program is specified.
#
# auth_param ntlm program /path/to/samba/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
#
# "children" numberofchildren
# The number of authenticator processes to spawn (no default). If you
# start too few Squid will have to wait for them to process a backlog
# of credential verifications, slowing it down. When credential
# verifications are done via a (slow) network you are likely to need
# lots of authenticator processes.
# auth_param ntlm children 5
#
# "max_challenge_reuses" number
# The maximum number of times a challenge given by a ntlm authentication
# helper can be reused. Increasing this number increases your exposure
# to replay attacks on your network. 0 (the default) means use the
# challenge is used only once. See also the max_ntlm_challenge_lifetime
# directive if enabling challenge reuses.
# auth_param ntlm max_challenge_reuses 0
#
# "max_challenge_lifetime" timespan
# The maximum time period a ntlm challenge is reused over. The
# actual period will be the minimum of this time AND the number of
# reused challenges.
# auth_param ntlm max_challenge_lifetime 2 minutes
#
# "use_ntlm_negotiate" on|off
# Enables support for NTLM NEGOTIATE packet exchanges with the helper.
# The configured ntlm authenticator must be able to handle NTLM
# NEGOTIATE packet. See the authenticator programs documentation if
# unsure. ntlm_auth from Samba-3.0.2 or later supports the use of this
# option.
# The NEGOTIATE packet is required to support NTLMv2 and a
# number of other negotiable NTLMSSP options, and also makes it
# more likely the negotiation is successful. Enabling this parameter
# will also solve problems encountered when NT domain policies
# restrict users to access only certain workstations. When this is off,
# all users must be allowed to log on the proxy servers too, or they'll
# get "invalid workstation" errors - and access denied - when trying to
# use Squid's services.
# Use of ntlm NEGOTIATE is incompatible with challenge reuse, so
# enabling this parameter will OVERRIDE the max_challenge_reuses and
# max_challenge_lifetime parameters and set them to 0.
# auth_param ntlm use_ntlm_negotiate off
#
#Recommended minimum configuration:
#auth_param digest program
#auth_param digest children 5
#auth_param digest realm Squid proxy-caching web server
#auth_param digest nonce_garbage_interval 5 minutes
#auth_param digest nonce_max_duration 30 minutes
#auth_param digest nonce_max_count 50
#auth_param ntlm program
#auth_param ntlm children 5
#auth_param ntlm max_challenge_reuses 0
#auth_param ntlm max_challenge_lifetime 2 minutes
#auth_param ntlm use_ntlm_negotiate off
#auth_param basic program
auth_param basic children 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours
auth_param basic casesensitive off

# TAG: authenticate_cache_garbage_interval
# The time period between garbage collection across the username cache.
# This is a tradeoff between memory utilization (long intervals - say
# 2 days) and CPU (short intervals - say 1 minute). Only change if you
# have good reason to.
#
#Default:
# authenticate_cache_garbage_interval 1 hour

# TAG: authenticate_ttl
# The time a user & their credentials stay in the logged in user cache
# since their last request. When the garbage interval passes, all user
# credentials that have passed their TTL are removed from memory.
#
#Default:
# authenticate_ttl 1 hour

# TAG: authenticate_ip_ttl
# If you use proxy authentication and the 'max_user_ip' ACL, this
# directive controls how long Squid remembers the IP addresses
# associated with each user. Use a small value (e.g., 60 seconds) if
# your users might change addresses quickly, as is the case with
# dialups. You might be safe using a larger value (e.g., 2 hours) in a
# corporate LAN environment with relatively static address assignments.
#
#Default:
# authenticate_ip_ttl 0 seconds

# TAG: external_acl_type
# This option defines external acl classes using a helper program to
# look up the status
#
# external_acl_type name [options] FORMAT.. /path/to/helper [helper arguments..]
#
# Options:
#
# ttl=n TTL in seconds for cached results (defaults to 3600
# for 1 hour)
# negative_ttl=n
# TTL for cached negative lookups (default same
# as ttl)
# children=n Concurrency level / number of processes spawn
# to service external acl lookups of this type.
# Note: see compatibility note below
# cache=n result cache size, 0 is unbounded (default)
# protocol=3.0 Use URL-escaped strings instead of quoting
#
# FORMAT specifications
#
# %LOGIN Authenticated user login name
# %IDENT Ident user name
# %SRC Client IP
# %DST Requested host
# %PROTO Requested protocol
# %PORT Requested port
# %METHOD Request method
# %{Header} HTTP request header
# %{Hdr:member} HTTP request header list member
# %{Hdr:;member}
# HTTP request header list member using ; as
# list separator. ; can be any non-alphanumeric
# character.
#
# In addition, any string specified in the referencing acl will
# also be included in the helper request line, after the specified
# formats (see the "acl external" directive)
#
# The helper receives lines per the above format specification,
# and returns lines starting with OK or ERR indicating the validity
# of the request and optionally followed by additional keywords with
# more details.
#
# General result syntax:
#
# OK/ERR keyword=value ...
#
# Defined keywords:
#
# user= The users name (login)
# error= Error description (only defined for ERR results)
#
# Keyword values need to be enclosed in quotes if they may contain
# whitespace, or the whitespace escaped using \. Any quotes or \
# characters within the keyword value must be \ escaped.
#
# If protocol=3.0 then URL escaping of the strings is used instead
# of the above described quoting format.
#
# Compatibility Note: The children= option was named concurrency= in
# Squid-2.5.STABLE3 and earlier and such syntax is still accepted to
# keep compatibility within the Squid-2.5 release. However, the meaning
# of concurrency= option has changed in Squid-3 and the old syntax of
# the directive is therefore deprecated from Squid-2.5.STABLE4 and later.
# If you want to be able to easily downgrade to earlier Squid-2.5
# releases you may want to continue using the old name, if not
# please use the new name.
#
#Default:
# none

# OPTIONS FOR TUNING THE CACHE
# -----------------------------------------------------------------------------

# TAG: wais_relay_host
# TAG: wais_relay_port
# Relay WAIS request to host (1st arg) at port (2 arg).
#
#Default:
# wais_relay_port 0

# TAG: request_header_max_size (KB)
# This specifies the maximum size for HTTP headers in a request.
# Request headers are usually relatively small (about 512 bytes).
# Placing a limit on the request header size will catch certain
# bugs (for example with persistent connections) and possibly
# buffer-overflow or denial-of-service attacks.
#
#Default:
# request_header_max_size 20 KB

# TAG: request_body_max_size (KB)
# This specifies the maximum size for an HTTP request body.
# In other words, the maximum size of a PUT/POST request.
# A user who attempts to send a request with a body larger
# than this limit receives an "Invalid Request" error message.
# If you set this parameter to a zero (the default), there will
# be no limit imposed.
#
#Default:
# request_body_max_size 0 KB

# TAG: refresh_pattern
# usage: refresh_pattern [-i] regex min percent max [options]
#
# By default, regular expressions are CASE-SENSITIVE. To make
# them case-insensitive, use the -i option.
#
# 'Min' is the time (in minutes) an object without an explicit
# expiry time should be considered fresh. The recommended
# value is 0, any higher values may cause dynamic applications
# to be erroneously cached unless the application designer
# has taken the appropriate actions.
#
# 'Percent' is a percentage of the objects age (time since last
# modification age) an object without explicit expiry time
# will be considered fresh.
#
# 'Max' is an upper limit on how long objects without an explicit
# expiry time will be considered fresh.
#
# options: override-expire
# override-lastmod
# reload-into-ims
# ignore-reload
#
# override-expire enforces min age even if the server
# sent a Expires: header. Doing this VIOLATES the HTTP
# standard. Enabling this feature could make you liable
# for problems which it causes.
#
# override-lastmod enforces min age even on objects
# that were modified recently.
#
# reload-into-ims changes client no-cache or ``reload''
# to If-Modified-Since requests. Doing this VIOLATES the
# HTTP standard. Enabling this feature could make you
# liable for problems which it causes.
#
# ignore-reload ignores a client no-cache or ``reload''
# header. Doing this VIOLATES the HTTP standard. Enabling
# this feature could make you liable for problems which
# it causes.
#
# Basically a cached object is:
#
# FRESH if expires < now, else STALE
# STALE if age > max
# FRESH if lm-factor < percent, else STALE
# FRESH if age < min
# else STALE
#
# The refresh_pattern lines are checked in the order listed here.
# The first entry which matches is used. If none of the entries
# match the default will be used.
#
# Note, you must uncomment all the default lines if you want
# to change one. The default setting is only active if none is
# used.
#
#Suggested default:
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320

# TAG: quick_abort_min (KB)
# TAG: quick_abort_max (KB)
# TAG: quick_abort_pct (percent)
# The cache by default continues downloading aborted requests
# which are almost completed (less than 16 KB remaining). This
# may be undesirable on slow (e.g. SLIP) links and/or very busy
# caches. Impatient users may tie up file descriptors and
# bandwidth by repeatedly requesting and immediately aborting
# downloads.
#
# When the user aborts a request, Squid will check the
# quick_abort values to the amount of data transfered until
# then.
#
# If the transfer has less than 'quick_abort_min' KB remaining,
# it will finish the retrieval.
#
# If the transfer has more than 'quick_abort_max' KB remaining,
# it will abort the retrieval.
#
# If more than 'quick_abort_pct' of the transfer has completed,
# it will finish the retrieval.
#
# If you do not want any retrieval to continue after the client
# has aborted, set both 'quick_abort_min' and 'quick_abort_max'
# to '0 KB'.
#
# If you want retrievals to always continue if they are being
# cached set 'quick_abort_min' to '-1 KB'.
#
#Default:
# quick_abort_min 16 KB
# quick_abort_max 16 KB
# quick_abort_pct 95

# TAG: negative_ttl time-units
# Time-to-Live (TTL) for failed requests. Certain types of
# failures (such as "connection refused" and "404 Not Found") are
# negatively-cached for a configurable amount of time. The
# default is 5 minutes. Note that this is different from
# negative caching of DNS lookups.
#
#Default:
# negative_ttl 5 minutes

# TAG: positive_dns_ttl time-units
# Upper limit on how long Squid will cache positive DNS responses.
# Default is 6 hours (360 minutes). This directive must be set
# larger than negative_dns_ttl.
#
#Default:
# positive_dns_ttl 6 hours

# TAG: negative_dns_ttl time-units
# Time-to-Live (TTL) for negative caching of failed DNS lookups.
# This also makes sets the lower cache limit on positive lookups.
# Minimum value is 1 second, and it is not recommendable to go
# much below 10 seconds.
#
#Default:
# negative_dns_ttl 1 minute

# TAG: range_offset_limit (bytes)
# Sets a upper limit on how far into the the file a Range request
# may be to cause Squid to prefetch the whole file. If beyond this
# limit Squid forwards the Range request as it is and the result
# is NOT cached.
#
# This is to stop a far ahead range request (lets say start at 17MB)
# from making Squid fetch the whole object up to that point before
# sending anything to the client.
#
# A value of -1 causes Squid to always fetch the object from the
# beginning so it may cache the result. (2.0 style)
#
# A value of 0 causes Squid to never fetch more than the
# client requested. (default)
#
#Default:
# range_offset_limit 0 KB

# TIMEOUTS
# -----------------------------------------------------------------------------

# TAG: forward_timeout time-units
# This parameter specifies how long Squid should at most attempt in
# finding a forwarding path for the request before giving up.
#
#Default:
# forward_timeout 4 minutes

# TAG: connect_timeout time-units
# This parameter specifies how long to wait for the TCP connect to
# the requested server or peer to complete before Squid should
# attempt to find another path where to forward the request.
#
#Default:
# connect_timeout 1 minute

# TAG: peer_connect_timeout time-units
# This parameter specifies how long to wait for a pending TCP
# connection to a peer cache. The default is 30 seconds. You
# may also set different timeout values for individual neighbors
# with the 'connect-timeout' option on a 'cache_peer' line.
#
#Default:
# peer_connect_timeout 30 seconds

# TAG: read_timeout time-units
# The read_timeout is applied on server-side connections. After
# each successful read(), the timeout will be extended by this
# amount. If no data is read again after this amount of time,
# the request is aborted and logged with ERR_READ_TIMEOUT. The
# default is 15 minutes.
#
#Default:
# read_timeout 15 minutes

# TAG: request_timeout
# How long to wait for an HTTP request after initial
# connection establishment.
#
#Default:
# request_timeout 5 minutes

# TAG: persistent_request_timeout
# How long to wait for the next HTTP request on a persistent
# connection after the previous request completes.
#
#Default:
# persistent_request_timeout 1 minute

# TAG: client_lifetime time-units
# The maximum amount of time a client (browser) is allowed to
# remain connected to the cache process. This protects the Cache
# from having a lot of sockets (and hence file descriptors) tied up
# in a CLOSE_WAIT state from remote clients that go away without
# properly shutting down (either because of a network failure or
# because of a poor client implementation). The default is one
# day, 1440 minutes.
#
# NOTE: The default value is intended to be much larger than any
# client would ever need to be connected to your cache. You
# should probably change client_lifetime only as a last resort.
# If you seem to have many client connections tying up
# filedescriptors, we recommend first tuning the read_timeout,
# request_timeout, persistent_request_timeout and quick_abort values.
#
#Default:
# client_lifetime 1 day

# TAG: half_closed_clients
# Some clients may shutdown the sending side of their TCP
# connections, while leaving their receiving sides open. Sometimes,
# Squid can not tell the difference between a half-closed and a
# fully-closed TCP connection. By default, half-closed client
# connections are kept open until a read(2) or write(2) on the
# socket returns an error. Change this option to 'off' and Squid
# will immediately close client connections when read(2) returns
# "no more data to read."
#
#Default:
# half_closed_clients on

# TAG: pconn_timeout
# Timeout for idle persistent connections to servers and other
# proxies.
#
#Default:
# pconn_timeout 120 seconds

# TAG: ident_timeout
# Maximum time to wait for IDENT lookups to complete.
#
# If this is too high, and you enabled IDENT lookups from untrusted
# users, you might be susceptible to denial-of-service by having
# many ident requests going at once.
#
#Default:
# ident_timeout 10 seconds

# TAG: shutdown_lifetime time-units
# When SIGTERM or SIGHUP is received, the cache is put into
# "shutdown pending" mode until all active sockets are closed.
# This value is the lifetime to set for all open descriptors
# during shutdown mode. Any active clients after this many
# seconds will receive a 'timeout' message.
#
#Default:
# shutdown_lifetime 30 seconds

# ACCESS CONTROLS
# -----------------------------------------------------------------------------

# TAG: acl
# Defining an Access List
#
# acl aclname acltype string1 ...
# acl aclname acltype "file" ...
#
# when using "file", the file should contain one item per line
#
# acltype is one of the types described below
#
# By default, regular expressions are CASE-SENSITIVE. To make
# them case-insensitive, use the -i option.
#
# acl aclname src ip-address/netmask ... (clients IP address)
# acl aclname src addr1-addr2/netmask ... (range of addresses)
# acl aclname dst ip-address/netmask ... (URL host's IP address)
# acl aclname myip ip-address/netmask ... (local socket IP address)
#
# acl aclname arp mac-address ... (xx:xx:xx:xx:xx:xx notation)
# # The arp ACL requires the special configure option --enable-arp-acl.
# # Furthermore, the arp ACL code is not portable to all operating systems.
# # It works on Linux, Solaris, FreeBSD and some other *BSD variants.
# #
# # NOTE: Squid can only determine the MAC address for clients that are on
# # the same subnet. If the client is on a different subnet, then Squid cannot
# # find out its MAC address.
#
# acl aclname srcdomain .foo.com ... # reverse lookup, client IP
# acl aclname dstdomain .foo.com ... # Destination server from URL
# acl aclname srcdom_regex [-i] xxx ... # regex matching client name
# acl aclname dstdom_regex [-i] xxx ... # regex matching server
# # For dstdomain and dstdom_regex a reverse lookup is tried if a IP
# # based URL is used and no match is found. The name "none" is used
# # if the reverse lookup fails.
#
# acl aclname time [day-abbrevs] [h1:m1-h2:m2]
# day-abbrevs:
# S - Sunday
# M - Monday
# T - Tuesday
# W - Wednesday
# H - Thursday
# F - Friday
# A - Saturday
# h1:m1 must be less than h2:m2
# acl aclname url_regex [-i] ^http:// ... # regex matching on whole URL
# acl aclname urlpath_regex [-i] \.gif$ ... # regex matching on URL path
# acl aclname urllogin [-i] [^a-zA-Z0-9] ... # regex matching on URL login field
# acl aclname port 80 70 21 ...
# acl aclname port 0-1024 ... # ranges allowed
# acl aclname myport 3128 ... # (local socket TCP port)
# acl aclname proto HTTP FTP ...
# acl aclname method GET POST ...
# acl aclname browser [-i] regexp ...
# # pattern match on User-Agent header (see also req_header below)
# acl aclname referer_regex [-i] regexp ...
# # pattern match on Referer header
# # Referer is highly unreliable, so use with care
# acl aclname ident username ...
# acl aclname ident_regex [-i] pattern ...
# # string match on ident output.
# # use REQUIRED to accept any non-null ident.
# acl aclname src_as number ...
# acl aclname dst_as number ...
# # Except for access control, AS numbers can be used for
# # routing of requests to specific caches. Here's an
# # example for routing all requests for AS#1241 and only
# # those to mycache.mydomain.net:
# # acl asexample dst_as 1241
# # cache_peer_access mycache.mydomain.net allow asexample
# # cache_peer_access mycache_mydomain.net deny all
#
# acl aclname proxy_auth username ...
# acl aclname proxy_auth_regex [-i] pattern ...
# # list of valid usernames
# # use REQUIRED to accept any valid username.
# #
# # NOTE: when a Proxy-Authentication header is sent but it is not
# # needed during ACL checking the username is NOT logged
# # in access.log.
# #
# # NOTE: proxy_auth requires a EXTERNAL authentication program
# # to check username/password combinations (see
# # auth_param directive).
# #
# # WARNING: proxy_auth can't be used in a transparent proxy. It
# # collides with any authentication done by origin servers. It may
# # seem like it works at first, but it doesn't.
#
# acl aclname snmp_community string ...
# # A community string to limit access to your SNMP Agent
# # Example:
# #
# # acl snmppublic snmp_community public
#
# acl aclname maxconn number
# # This will be matched when the client's IP address has
# # more than HTTP connections established.
#
# acl aclname max_user_ip [-s] number
# # This will be matched when the user attempts to log in from more
# # than different ip addresses. The authenticate_ip_ttl
# # parameter controls the timeout on the ip entries.
# # If -s is specified the limit is strict, denying browsing
# # from any further IP addresses until the ttl has expired. Without
# # -s Squid will just annoy the user by "randomly" denying requests.
# # (the counter is reset each time the limit is reached and a
# # request is denied)
# # NOTE: in acceleration mode or where there is mesh of child proxies,
# # clients may appear to come from multiple addresses if they are
# # going through proxy farms, so a limit of 1 may cause user problems.
#
# acl aclname req_mime_type mime-type1 ...
# # regex match against the mime type of the request generated
# # by the client. Can be used to detect file upload or some
# # types HTTP tunneling requests.
# # NOTE: This does NOT match the reply. You cannot use this
# # to match the returned file type.
#
# acl aclname req_header header-name [-i] any\.regex\.here
# # regex match against any of the known request headers. May be
# # thought of as a superset of "browser", "referer" and "mime-type"
# # ACLs.
#
# acl aclname rep_mime_type mime-type1 ...
# # regex match against the mime type of the reply received by
# # squid. Can be used to detect file download or some
# # types HTTP tunneling requests.
# # NOTE: This has no effect in http_access rules. It only has
# # effect in rules that affect the reply data stream such as
# # http_reply_access.
#
# acl aclname rep_header header-name [-i] any\.regex\.here
# # regex match against any of the known response headers.
# # Example:
# #
# # acl many_spaces rep_header Content-Disposition -i [[:space:]]{3,}
#
# acl acl_name external class_name [arguments...]
# # external ACL lookup via a helper class defined by the
# # external_acl_type directive.
#
#Examples:
#acl macaddress arp 09:00:2b:23:45:67
#acl myexample dst_as 1241
#acl password proxy_auth REQUIRED
#acl fileupload req_mime_type -i ^multipart/form-data$
#acl javascript rep_mime_type -i ^application/x-javascript$
#
#Recommended minimum configuration:
acl all src 0.0.0.0/0.0.0.0

#################################################
acl net2 src 192.168.0.200/32
acl net2 src 192.168.0.10/32
acl net2 src 192.168.0.11/32
acl net3 src 192.168.0.101/32
acl net3 src 192.168.0.27/32
acl net3 src 192.168.0.41/32
acl net src 192.168.1.0/255.255.255.0
##################################################

acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#acl dl1 url_regex -i "/etc/squid/ban"
#acl abc url_regex -i cgi-bin passport gateway google gmail

######################## Windows Update Block ###########
acl abc2 url_regex -i ^http://du.download.windowsupdate.com
acl abc2 url_regex -i ^http://download.windowsupdate.com
acl abc2 url_regex -i ^http://www.download.windowsupdate.com
#########################

acl opendl time 11:00-23:59
acl opendl time 00:00-01:00

# TAG: follow_x_forwarded_for
# Allowing or Denying the X-Forwarded-For header to be followed to
# find the original source of a request.
#
# Requests may pass through a chain of several other proxies
# before reaching us. The X-Forwarded-For header will contain a
# comma-separated list of the IP addresses in the chain, with the
# rightmost address being the most recent.
#
# If a request reaches us from a source that is allowed by this
# configuration item, then we consult the X-Forwarded-For header
# to see where that host received the request from. If the
# X-Forwarded-For header contains multiple addresses, and if
# acl_uses_indirect_client is on, then we continue backtracking
# until we reach an address for which we are not allowed to
# follow the X-Forwarded-For header, or until we reach the first
# address in the list. (If acl_uses_indirect_client is off, then
# it's impossible to backtrack through more than one level of
# X-Forwarded-For addresses.)
#
# The end result of this process is an IP address that we will
# refer to as the indirect client address. This address may
# be treated as the client address for access control, delay
# pools and logging, depending on the acl_uses_indirect_client,
# delay_pool_uses_indirect_client and log_uses_indirect_client
# options.
#
# SECURITY CONSIDERATIONS:
#
# Any host for which we follow the X-Forwarded-For header
# can place incorrect information in the header, and Squid
# will use the incorrect information as if it were the
# source address of the request. This may enable remote
# hosts to bypass any access control restrictions that are
# based on the client's source addresses.
#
# For example:
#
# acl localhost src 127.0.0.1
# acl my_other_proxy srcdomain .proxy.example.com
# follow_x_forwarded_for allow localhost
# follow_x_forwarded_for allow my_other_proxy
#
#Default:
# follow_x_forwarded_for deny all

# TAG: acl_uses_indirect_client on|off
# Controls whether the indirect client address
# (see follow_x_forwarded_for) is used instead of the
# direct client address in acl matching.
#
#Default:
# acl_uses_indirect_client on

# TAG: delay_pool_uses_indirect_client on|off
# Controls whether the indirect client address
# (see follow_x_forwarded_for) is used instead of the
# direct client address in delay pools.
#
#Default:
# delay_pool_uses_indirect_client on

# TAG: log_uses_indirect_client on|off
# Controls whether the indirect client address
# (see follow_x_forwarded_for) is used instead of the
# direct client address in the access log.
#
#Default:
# log_uses_indirect_client on

# TAG: http_access
# Allowing or Denying access based on defined access lists
#
# Access to the HTTP port:
# http_access allow|deny [!]aclname ...
#
# NOTE on default values:
#
# If there are no "access" lines present, the default is to deny
# the request.
#
# If none of the "access" lines cause a match, the default is the
# opposite of the last line in the list. If the last line was
# deny, the default is allow. Conversely, if the last line
# is allow, the default will be deny. For these reasons, it is a
# good idea to have an "deny all" or "allow all" entry at the end
# of your access lists to avoid potential confusion.
#
#Default:
# http_access deny all
#
#Recommended minimum configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager
# Deny requests to unknown ports
http_access deny !Safe_ports
# Deny CONNECT to other than SSL ports
http_access deny CONNECT !SSL_ports
#
# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS

# Example rule allowing access from your local networks. Adapt
# to list your (internal) IP networks from where browsing should
# be allowed
#acl our_networks src 192.168.1.0/24 192.168.2.0/24
#http_access allow our_networks

# And finally deny all other access to this proxy
http_access allow localhost

http_access deny abc2
http_access allow net
http_access allow net2

http_access deny all

# TAG: http_reply_access
# Allow replies to client requests. This is complementary to http_access.
#
# http_reply_access allow|deny [!] aclname ...
#
# NOTE: if there are no access lines present, the default is to allow
# all replies
#
# If none of the access lines cause a match the opposite of the
# last line will apply. Thus it is good practice to end the rules
# with an "allow all" or "deny all" entry.
#
#Default:
http_reply_access allow all
#
#Recommended minimum configuration:
#
# Insert your own rules here.
#
#
# and finally allow by default
http_reply_access allow all

# TAG: icp_access
# Allowing or Denying access to the ICP port based on defined
# access lists
#
# icp_access allow|deny [!]aclname ...
#
# See http_access for details
#
#Default:
# icp_access deny all
#
#Allow ICP queries from everyone
icp_access allow all

# TAG: miss_access
# Use to force your neighbors to use you as a sibling instead of
# a parent. For example:
#
# acl localclients src 172.16.0.0/16
# miss_access allow localclients
# miss_access deny !localclients
#
# This means only your local clients are allowed to fetch
# MISSES and all other clients can only fetch HITS.
#
# By default, allow all clients who passed the http_access rules
# to fetch MISSES from us.
#
#Default setting:
# miss_access allow all

# TAG: cache_peer_access
# Similar to 'cache_peer_domain' but provides more flexibility by
# using ACL elements.
#
# cache_peer_access cache-host allow|deny [!]aclname ...
#
# The syntax is identical to 'http_access' and the other lists of
# ACL elements. See the comments for 'http_access' below, or
# the Squid FAQ (http://www.squid-cache.org/FAQ/FAQ-10.html).
#
#Default:
# none

# TAG: ident_lookup_access
# A list of ACL elements which, if matched, cause an ident
# (RFC931) lookup to be performed for this request. For
# example, you might choose to always perform ident lookups
# for your main multi-user Unix boxes, but not for your Macs
# and PCs. By default, ident lookups are not performed for
# any requests.
#
# To enable ident lookups for specific client addresses, you
# can follow this example:
#
# acl ident_aware_hosts src 198.168.1.0/255.255.255.0
# ident_lookup_access allow ident_aware_hosts
# ident_lookup_access deny all
#
# Only src type ACL checks are fully supported. A src_domain
# ACL might work at times, but it will not always provide
# the correct result.
#
#Default:
# ident_lookup_access deny all

# TAG: tcp_outgoing_tos
# Allows you to select a TOS/Diffserv value to mark outgoing
# connections with, based on the username or source address
# making the request.
#
# tcp_outgoing_tos ds-field [!]aclname ...
#
# Example where normal_service_net uses the TOS value 0x00
# and normal_service_net uses 0x20
#
# acl normal_service_net src 10.0.0.0/255.255.255.0
# acl good_service_net src 10.0.1.0/255.255.255.0
# tcp_outgoing_tos 0x00 normal_service_net 0x00
# tcp_outgoing_tos 0x20 good_service_net
#
# TOS/DSCP values really only have local significance - so you should
# know what you're specifying. For more information, see RFC2474 and
# RFC3260.
#
# The TOS/DSCP byte must be exactly that - a octet value 0 - 255, or
# "default" to use whatever default your host has. Note that in
# practice often only values 0 - 63 is usable as the two highest bits
# have been redefined for use by ECN (RFC3168).
#
# Processing proceeds in the order specified, and stops at first fully
# matching line.
#
# Note: The use of this directive using client dependent ACLs is
# incompatible with the use of server side persistent connetions. To
# ensure correct results it is best to set server_persisten_connections
# to off when using this directive in such configurations.
#
#Default:
# none

# TAG: tcp_outgoing_address
# Allows you to map requests to different outgoing IP addresses
# based on the username or sourceaddress of the user making
# the request.
#
# tcp_outgoing_address ipaddr [[!]aclname] ...
#
# Example where requests from 10.0.0.0/24 will be forwarded
# with source address 10.1.0.1, 10.0.2.0/24 forwarded with
# source address 10.1.0.2 and the rest will be forwarded with
# source address 10.1.0.3.
#
# acl normal_service_net src 10.0.0.0/255.255.255.0
# acl good_service_net src 10.0.1.0/255.255.255.0
# tcp_outgoing_address 10.0.0.1 normal_service_net
# tcp_outgoing_address 10.0.0.2 good_service_net
# tcp_outgoing_address 10.0.0.3
#
# Processing proceeds in the order specified, and stops at first fully
# matching line.
#
# Note: The use of this directive using client dependent ACLs is
# incompatible with the use of server side persistent connetions. To
# ensure correct results it is best to set server_persisten_connections
# to off when using this directive in such configurations.
#
#Default:
# none

# TAG: reply_header_max_size (KB)
# This specifies the maximum size for HTTP headers in a reply.
# Reply headers are usually relatively small (about 512 bytes).
# Placing a limit on the reply header size will catch certain
# bugs (for example with persistent connections) and possibly
# buffer-overflow or denial-of-service attacks.
#
#Default:
# reply_header_max_size 20 KB

# TAG: reply_body_max_size bytes allow|deny acl acl...
# This option specifies the maximum size of a reply body in bytes.
# It can be used to prevent users from downloading very large files,
# such as MP3's and movies. When the reply headers are received,
# the reply_body_max_size lines are processed, and the first line with
# a result of "allow" is used as the maximum body size for this reply.
# This size is checked twice. First when we get the reply headers,
# we check the content-length value. If the content length value exists
# and is larger than the allowed size, the request is denied and the
# user receives an error message that says "the request or reply
# is too large." If there is no content-length, and the reply
# size exceeds this limit, the client's connection is just closed
# and they will receive a partial reply.
#
# WARNING: downstream caches probably can not detect a partial reply
# if there is no content-length header, so they will cache
# partial responses and give them out as hits. You should NOT
# use this option if you have downstream caches.
#
# If you set this parameter to zero (the default), there will be
# no limit imposed.
#
#Default:
# reply_body_max_size 0 allow all

# ADMINISTRATIVE PARAMETERS
# -----------------------------------------------------------------------------

# TAG: cache_mgr
# Email-address of local cache manager who will receive
# mail if the cache dies. The default is "root".
#

cache_mgr imrance@hotmail.com
#Default:
# cache_mgr root

# TAG: mail_from
# From: email-address for mail sent when the cache dies.
# The default is to use 'appname@unique_hostname'.
# Default appname value is "squid", can be changed into
# src/globals.h before building squid.
#
#Default:
# none

# TAG: mail_program
# Email program used to send mail if the cache dies.
# The default is "mail". The specified program must complain
# with the standard Unix mail syntax:
# mail_program recipient < mailfile
# Optional command line options can be specified.
#
#Default:
# mail_program mail

# TAG: cache_effective_user
# If you start Squid as root, it will change its effective/real
# UID/GID to the user specified below. The default is to change
# to UID to "squid". If you define cache_effective_user, but not
# cache_effective_group, Squid sets the GID to the effective
# user's default group ID (taken from the password file) and
# supplementary group list from the from groups membership of
# cache_effective_user.
cache_effective_user squid
#
#Default:
# cache_effective_user squid

# TAG: cache_effective_group
# If you want Squid to run with a specific GID regardless of
# the group memberships of the effective user then set this
# to the group (or GID) you want Squid to run as. When set
# all other group privileges of the effective user is ignored
# and only this GID is effective. If Squid is not started as
# root the user starting Squid must be member of the specified
# group.
cache_effective_group squid
#
#Default:
# cache_effective_group squid

visible_hostname proxy.rays.net
# TAG: visible_hostname
# If you want to present a special hostname in error messages, etc,
# define this. Otherwise, the return value of gethostname()
# will be used. If you have multiple caches in a cluster and
# get errors about IP-forwarding you must set them to have individual
# names with this setting.
#
#Default:
# none

# TAG: unique_hostname
# If you want to have multiple machines with the same
# 'visible_hostname' you must give each machine a different
# 'unique_hostname' so forwarding loops can be detected.
#
#Default:
# none

# TAG: hostname_aliases
# A list of other DNS names your cache has.
#
#Default:
# none

# OPTIONS FOR THE CACHE REGISTRATION SERVICE
# -----------------------------------------------------------------------------
#
# This section contains parameters for the (optional) cache
# announcement service. This service is provided to help
# cache administrators locate one another in order to join or
# create cache hierarchies.
#
# An 'announcement' message is sent (via UDP) to the registration
# service by Squid. By default, the announcement message is NOT
# SENT unless you enable it with 'announce_period' below.
#
# The announcement message includes your hostname, plus the
# following information from this configuration file:
#
# http_port
# icp_port
# cache_mgr
#
# All current information is processed regularly and made
# available on the Web at http://www.ircache.net/Cache/Tracker/.

# TAG: announce_period
# This is how frequently to send cache announcements. The
# default is `0' which disables sending the announcement
# messages.
#
# To enable announcing your cache, just uncomment the line
# below.
#
#Default:
# announce_period 0
#
#To enable announcing your cache, just uncomment the line below.
#announce_period 1 day

# TAG: announce_host
# TAG: announce_file
# TAG: announce_port
# announce_host and announce_port set the hostname and port
# number where the registration message will be sent.
#
# Hostname will default to 'tracker.ircache.net' and port will
# default default to 3131. If the 'filename' argument is given,
# the contents of that file will be included in the announce
# message.
#
#Default:
# announce_host tracker.ircache.net
# announce_port 3131

# HTTPD-ACCELERATOR OPTIONS
# -----------------------------------------------------------------------------

httpd_accel_host virtual
# TAG: httpd_accel_host
# TAG: httpd_accel_port
# If you want to run Squid as an httpd accelerator, define the
# host name and port number where the real HTTP server is.
#
# If you want IP based virtual host support specify the
# hostname as "virtual". This will make Squid use the IP address
# where it accepted the request as hostname in the URL.
#
# If you want virtual port support specify the port as "0".
#
# NOTE: enabling httpd_accel_host disables proxy-caching and
# ICP. If you want these features enabled also, set
# the 'httpd_accel_with_proxy' option.
#
#Default:
httpd_accel_port 80

# TAG: httpd_accel_single_host on|off
# If you are running Squid as an accelerator and have a single backend
# server set this to on. This causes Squid to forward the request
# to this server, regardless of what any redirectors or Host headers
# say.
#
# Leave this at off if you have multiple backend servers, and use a
# redirector (or host table or private DNS) to map the requests to the
# appropriate backend servers. Note that the mapping needs to be a
# 1-1 mapping between requested and backend (from redirector) domain
# names or caching will fail, as caching is performed using the
# URL returned from the redirector.
#
# See also redirect_rewrites_host_header.
#
#Default:
# httpd_accel_single_host off

# TAG: httpd_accel_with_proxy on|off
# If you want to use Squid as both a local httpd accelerator
# and as a proxy, change this to 'on'. Note however your
# proxy users may have trouble to reach the accelerated domains
# unless their browsers are configured not to use this proxy for
# those domains (for example via the no_proxy browser configuration
# setting)
#
#Default:
httpd_accel_with_proxy on

# TAG: httpd_accel_uses_host_header on|off
# HTTP/1.1 requests include a Host: header which is basically the
# hostname from the URL. The Host: header is used for domain based
# virtual hosts. If your accelerator needs to provide domain based
# virtual hosts on the same IP address you will need to turn this
# on.
#
# Note Squid does NOT check the value of the Host header matches
# any of your accelerated server, so it may open a big security hole
# unless you take care to set up access controls proper. We recommend
# this option remain disabled unless you are sure of what you
# are doing.
#
# However, you will need to enable this option if you run Squid
# as a transparent proxy. Otherwise, virtual servers which
# require the Host: header will not be properly cached.
#
#Default:
httpd_accel_uses_host_header on

# TAG: httpd_accel_no_pmtu_disc on|off
# In many setups of transparently intercepting proxies Path-MTU
# discovery can not work on traffic towards the clients. This is
# the case when the intercepting device does not fully track
# connections and fails to forward ICMP must fragment messages
# to the cache server.
#
# If you have such setup and experience that certain clients
# sporadically hang or never complete requests set this to on.
#
#Default:
# httpd_accel_no_pmtu_disc off

# MISCELLANEOUS
# -----------------------------------------------------------------------------

# TAG: dns_testnames
# The DNS tests exit as soon as the first site is successfully looked up
#
# This test can be disabled with the -D command line option.
#
#Default:
# dns_testnames netscape.com internic.net nlanr.net microsoft.com

# TAG: logfile_rotate
# Specifies the number of logfile rotations to make when you
# type 'squid -k rotate'. The default is 10, which will rotate
# with extensions 0 through 9. Setting logfile_rotate to 0 will
# disable the rotation, but the logfiles are still closed and
# re-opened. This will enable you to rename the logfiles
# yourself just before sending the rotate signal.
#
# Note, the 'squid -k rotate' command normally sends a USR1
# signal to the running squid process. In certain situations
# (e.g. on Linux with Async I/O), USR1 is used for other
# purposes, so -k rotate uses another signal. It is best to get
# in the habit of using 'squid -k rotate' instead of 'kill -USR1
# '.
#
logfile_rotate 10
#
#Default:
# logfile_rotate 0

# TAG: append_domain
# Appends local domain name to hostnames without any dots in
# them. append_domain must begin with a period.
#
# Be warned there are now Internet names with no dots in
# them using only top-domain names, so setting this may
# cause some Internet sites to become unavailable.
#
#Example:
# append_domain .yourdomain.com
#
#Default:
# none

# TAG: tcp_recv_bufsize (bytes)
# Size of receive buffer to set for TCP sockets. Probably just
# as easy to change your kernel's default. Set to zero to use
# the default buffer size.
#
#Default:
# tcp_recv_bufsize 0 bytes

# TAG: err_html_text
# HTML text to include in error messages. Make this a "mailto"
# URL to your admin address, or maybe just a link to your
# organizations Web page.
#
# To include this in your error messages, you must rewrite
# the error template files (found in the "errors" directory).
# Wherever you want the 'err_html_text' line to appear,
# insert a %L tag in the error template file.
#
#Default:
# none

# TAG: deny_info
# Usage: deny_info err_page_name acl
# or deny_info http://... acl
# Example: deny_info ERR_CUSTOM_ACCESS_DENIED bad_guys
#
# This can be used to return a ERR_ page for requests which
# do not pass the 'http_access' rules. A single ACL will cause
# the http_access check to fail. If a 'deny_info' line exists
# for that ACL Squid returns a corresponding error page.
#
# You may use ERR_ pages that come with Squid or create your own pages
# and put them into the configured errors/ directory.
#
# Alternatively you can specify an error URL. The browsers will
# get redirected (302) to the specified URL. %s in the redirection
# URL will be replaced by the requested URL.
#
# Alternatively you can tell Squid to reset the TCP connection
# by specifying TCP_RESET.
#
#Default:
# none

# TAG: memory_pools on|off
# If set, Squid will keep pools of allocated (but unused) memory
# available for future use. If memory is a premium on your
# system and you believe your malloc library outperforms Squid
# routines, disable this.
#
#Default:
memory_pools on

# TAG: memory_pools_limit (bytes)
# Used only with memory_pools on:
# memory_pools_limit 50 MB
#
# If set to a non-zero value, Squid will keep at most the specified
# limit of allocated (but unused) memory in memory pools. All free()
# requests that exceed this limit will be handled by your malloc
# library. Squid does not pre-allocate any memory, just safe-keeps
# objects that otherwise would be free()d. Thus, it is safe to set
# memory_pools_limit to a reasonably high value even if your
# configuration will use less memory.
#
# If set to zero, Squid will keep all memory it can. That is, there
# will be no limit on the total amount of memory used for safe-keeping.
#
# To disable memory allocation optimization, do not set
# memory_pools_limit to 0. Set memory_pools to "off" instead.
#
# An overhead for maintaining memory pools is not taken into account
# when the limit is checked. This overhead is close to four bytes per
# object kept. However, pools may actually _save_ memory because of
# reduced memory thrashing in your malloc library.
#
#Default:
# memory_pools_limit 5 MB

# TAG: forwarded_for on|off
# If set, Squid will include your system's IP address or name
# in the HTTP requests it forwards. By default it looks like
# this:
#
# X-Forwarded-For: 192.1.2.3
#
# If you disable this, it will appear as
#
# X-Forwarded-For: unknown
#
#Default:
# forwarded_for on

# TAG: log_icp_queries on|off
# If set, ICP queries are logged to access.log. You may wish
# do disable this if your ICP load is VERY high to speed things
# up or to simplify log analysis.
#
#Default:
# log_icp_queries on

# TAG: icp_hit_stale on|off
# If you want to return ICP_HIT for stale cache objects, set this
# option to 'on'. If you have sibling relationships with caches
# in other administrative domains, this should be 'off'. If you only
# have sibling relationships with caches under your control,
# it is probably okay to set this to 'on'.
# If set to 'on', your siblings should use the option "allow-miss"
# on their cache_peer lines for connecting to you.
#
#Default:
# icp_hit_stale off

# TAG: minimum_direct_hops
# If using the ICMP pinging stuff, do direct fetches for sites
# which are no more than this many hops away.
#
#Default:
# minimum_direct_hops 4

# TAG: minimum_direct_rtt
# If using the ICMP pinging stuff, do direct fetches for sites
# which are no more than this many rtt milliseconds away.
#
#Default:
# minimum_direct_rtt 400

# TAG: cachemgr_passwd
# Specify passwords for cachemgr operations.
#
# Usage: cachemgr_passwd password action action ...
#
# Some valid actions are (see cache manager menu for a full list):
# 5min
# 60min
# asndb
# authenticator
# cbdata
# client_list
# comm_incoming
# config *
# counters
# delay
# digest_stats
# dns
# events
# filedescriptors
# fqdncache
# histograms
# http_headers
# info
# io
# ipcache
# mem
# menu
# netdb
# non_peers
# objects
# offline_toggle *
# pconn
# peer_select
# redirector
# refresh
# server_list
# shutdown *
# store_digest
# storedir
# utilization
# via_headers
# vm_objects
#
# * Indicates actions which will not be performed without a
# valid password, others can be performed if not listed here.
#
# To disable an action, set the password to "disable".
# To allow performing an action without a password, set the
# password to "none".
#
# Use the keyword "all" to set the same password for all actions.
#
#Example:
# cachemgr_passwd secret shutdown
# cachemgr_passwd lesssssssecret info stats/objects
# cachemgr_passwd disable all
#
#Default:
# none

# TAG: store_avg_object_size (kbytes)
# Average object size, used to estimate number of objects your
# cache can hold. See doc/Release-Notes-1.1.txt. The default is
# 13 KB.
#
#Default:
# store_avg_object_size 13 KB

# TAG: store_objects_per_bucket
# Target number of objects per bucket in the store hash table.
# Lowering this value increases the total number of buckets and
# also the storage maintenance rate. The default is 50.
#
#Default:
# store_objects_per_bucket 20

# TAG: client_db on|off
# If you want to disable collecting per-client statistics,
# turn off client_db here.
#
#Default:
# client_db on

# TAG: netdb_low
# TAG: netdb_high
# The low and high water marks for the ICMP measurement
# database. These are counts, not percents. The defaults are
# 900 and 1000. When the high water mark is reached, database
# entries will be deleted until the low mark is reached.
#
#Default:
# netdb_low 900
# netdb_high 1000

# TAG: netdb_ping_period
# The minimum period for measuring a site. There will be at
# least this much delay between successive pings to the same
# network. The default is five minutes.
#
#Default:
# netdb_ping_period 5 minutes

# TAG: query_icmp on|off
# If you want to ask your peers to include ICMP data in their ICP
# replies, enable this option.
#
# If your peer has configured Squid (during compilation) with
# '--enable-icmp' that peer will send ICMP pings to origin server
# sites of the URLs it receives. If you enable this option the
# ICP replies from that peer will include the ICMP data (if available).
# Then, when choosing a parent cache, Squid will choose the parent with
# the minimal RTT to the origin server. When this happens, the
# hierarchy field of the access.log will be
# "CLOSEST_PARENT_MISS". This option is off by default.
#
#Default:
# query_icmp off

# TAG: test_reachability on|off
# When this is 'on', ICP MISS replies will be ICP_MISS_NOFETCH
# instead of ICP_MISS if the target host is NOT in the ICMP
# database, or has a zero RTT.
#
#Default:
# test_reachability off

# TAG: buffered_logs on|off
# cache.log log file is written with stdio functions, and as such
# it can be buffered or unbuffered. By default it will be unbuffered.
# Buffering it can speed up the writing slightly (though you are
# unlikely to need to worry unless you run with tons of debugging
# enabled in which case performance will suffer badly anyway..).
#
#Default:
# buffered_logs off

# TAG: reload_into_ims on|off
# When you enable this option, client no-cache or ``reload''
# requests will be changed to If-Modified-Since requests.
# Doing this VIOLATES the HTTP standard. Enabling this
# feature could make you liable for problems which it
# causes.
#
# see also refresh_pattern for a more selective approach.
#
#Default:
# reload_into_ims off

# TAG: always_direct
# Usage: always_direct allow|deny [!]aclname ...
#
# Here you can use ACL elements to specify requests which should
# ALWAYS be forwarded by Squid to the origin servers without using
# any peers. For example, to always directly forward requests for
# local servers ignoring any parents or siblings you may have use
# something like:
#
# acl local-servers dstdomain my.domain.net
# always_direct allow local-servers
#
# To always forward FTP requests directly, use
#
# acl FTP proto FTP
# always_direct allow FTP
#
# NOTE: There is a similar, but opposite option named
# 'never_direct'. You need to be aware that "always_direct deny
# foo" is NOT the same thing as "never_direct allow foo". You
# may need to use a deny rule to exclude a more-specific case of
# some other rule. Example:
#
# acl local-external dstdomain external.foo.net
# acl local-servers dstdomain .foo.net
# always_direct deny local-external
# always_direct allow local-servers
#
# NOTE: If your goal is to make the client forward the request
# directly to the origin server bypassing Squid then this needs
# to be done in the client configuration. Squid configuration
# can only tell Squid how Squid should fetch the object.
#
# NOTE: This directive is not related to caching. The replies
# is cached as usual even if you use always_direct. To not cache
# the replies see no_cache.
#
# This option replaces some v1.1 options such as local_domain
# and local_ip.
#
#Default:
# none

# TAG: never_direct
# Usage: never_direct allow|deny [!]aclname ...
#
# never_direct is the opposite of always_direct. Please read
# the description for always_direct if you have not already.
#
# With 'never_direct' you can use ACL elements to specify
# requests which should NEVER be forwarded directly to origin
# servers. For example, to force the use of a proxy for all
# requests, except those in your local domain use something like:
#
# acl local-servers dstdomain .foo.net
# acl all src 0.0.0.0/0.0.0.0
# never_direct deny local-servers
# never_direct allow all
#
# or if Squid is inside a firewall and there are local intranet
# servers inside the firewall use something like:
#
# acl local-intranet dstdomain .foo.net
# acl local-external dstdomain external.foo.net
# always_direct deny local-external
# always_direct allow local-intranet
# never_direct allow all
#
# This option replaces some v1.1 options such as inside_firewall
# and firewall_ip.
#
#Default:
# none

# TAG: header_access
# Usage: header_access header_name allow|deny [!]aclname ...
#
# WARNING: Doing this VIOLATES the HTTP standard. Enabling
# this feature could make you liable for problems which it
# causes.
#
# This option replaces the old 'anonymize_headers' and the
# older 'http_anonymizer' option with something that is much
# more configurable. This new method creates a list of ACLs
# for each header, allowing you very fine-tuned header
# mangling.
#
# You can only specify known headers for the header name.
# Other headers are reclassified as 'Other'. You can also
# refer to all the headers with 'All'.
#
# For example, to achieve the same behavior as the old
# 'http_anonymizer standard' option, you should use:
#
# header_access From deny all
# header_access Referer deny all
# header_access Server deny all
# header_access User-Agent deny all
# header_access WWW-Authenticate deny all
# header_access Link deny all
#
# Or, to reproduce the old 'http_anonymizer paranoid' feature
# you should use:
#
# header_access Allow allow all
# header_access Authorization allow all
# header_access WWW-Authenticate allow all
# header_access Cache-Control allow all
# header_access Content-Encoding allow all
# header_access Content-Length allow all
# header_access Content-Type allow all
# header_access Date allow all
# header_access Expires allow all
# header_access Host allow all
# header_access If-Modified-Since allow all
# header_access Last-Modified allow all
# header_access Location allow all
# header_access Pragma allow all
# header_access Accept allow all
# header_access Accept-Charset allow all
# header_access Accept-Encoding allow all
# header_access Accept-Language allow all
# header_access Content-Language allow all
# header_access Mime-Version allow all
# header_access Retry-After allow all
# header_access Title allow all
# header_access Connection allow all
# header_access Proxy-Connection allow all
# header_access All deny all
#
# By default, all headers are allowed (no anonymizing is
# performed).
#
#Default:
# none

# TAG: header_replace
# Usage: header_replace header_name message
# Example: header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)
#
# This option allows you to change the contents of headers
# denied with header_access above, by replacing them with
# some fixed string. This replaces the old fake_user_agent
# option.
#
# By default, headers are removed if denied.
#
#Default:
# none

# TAG: icon_directory
# Where the icons are stored. These are normally kept in
# /usr/share/squid/icons
#
#Default:
# icon_directory /usr/share/squid/icons

# TAG: global_internal_static
# This directive controls is Squid should intercept all requests for
# /squid-internal-static/ no matter which host the URL is requesting
# (default on setting), or if nothing special should be done for
# such URLs (off setting). The purpose of this directive is to make
# icons etc work better in complex cache hierarchies where it may
# not always be possible for all corners in the cache mesh to reach
# the server generating a directory listing.
#
#Default:
# global_internal_static on

# TAG: short_icon_urls
# If this is enabled Squid will use short URLs for icons.
#
# If off the URLs for icons will always be absolute URLs
# including the proxy name and port.
#
#Default:
# short_icon_urls off

# TAG: error_directory
# Directory where the error files are read from.
# /usr/lib/squid/errors contains sets of error files
# in different languages. The default error directory
# is /etc/squid/errors, which is a link to one of these
# error sets.
#
# If you wish to create your own versions of the error files,
# either to customize them to suit your language or company,
# copy the template English files to another
# directory and point this tag at them.
#
#error_directory /usr/share/squid/errors/English
#
#Default:
# error_directory /usr/share/squid/errors/English

# TAG: maximum_single_addr_tries
# This sets the maximum number of connection attempts for a
# host that only has one address (for multiple-address hosts,
# each address is tried once).
#
# The default value is one attempt, the (not recommended)
# maximum is 255 tries. A warning message will be generated
# if it is set to a value greater than ten.
#
# Note: This is in addition to the request re-forwarding which
# takes place if Squid fails to get a satisfying response.
#
#Default:
# maximum_single_addr_tries 1

# TAG: retry_on_error
# If set to on Squid will automatically retry requests when
# receiving an error response. This is mainly useful if you
# are in a complex cache hierarchy to work around access
# control errors.
#
#Default:
# retry_on_error off

# TAG: snmp_port
# Squid can now serve statistics and status information via SNMP.
# A value of "0" disables SNMP support. If you wish to use SNMP,
# set this to "3401" to use the normal SNMP support.
#
#Default:
# snmp_port 0

# TAG: snmp_access
# Allowing or denying access to the SNMP port.
#
# All access to the agent is denied by default.
# usage:
#
# snmp_access allow|deny [!]aclname ...
#
#Example:
# snmp_access allow snmppublic localhost
# snmp_access deny all
#
#Default:
# snmp_access deny all

# TAG: snmp_incoming_address
# TAG: snmp_outgoing_address
# Just like 'udp_incoming_address' above, but for the SNMP port.
#
# snmp_incoming_address is used for the SNMP socket receiving
# messages from SNMP agents.
# snmp_outgoing_address is used for SNMP packets returned to SNMP
# agents.
#
# The default snmp_incoming_address (0.0.0.0) is to listen on all
# available network interfaces.
#
# If snmp_outgoing_address is set to 255.255.255.255 (the default)
# it will use the same socket as snmp_incoming_address. Only
# change this if you want to have SNMP replies sent using another
# address than where this Squid listens for SNMP queries.
#
# NOTE, snmp_incoming_address and snmp_outgoing_address can not have
# the same value since they both use port 3401.
#
#Default:
# snmp_incoming_address 0.0.0.0
# snmp_outgoing_address 255.255.255.255

# TAG: as_whois_server
# WHOIS server to query for AS numbers. NOTE: AS numbers are
# queried only when Squid starts up, not for every request.
#
#Default:
# as_whois_server whois.ra.net
# as_whois_server whois.ra.net

# TAG: wccp_router
# Use this option to define your WCCP ``home'' router for
# Squid. Setting the 'wccp_router' to 0.0.0.0 (the default)
# disables WCCP.
#
#Default:
# wccp_router 0.0.0.0

# TAG: wccp_version
# According to some users, Cisco IOS 11.2 only supports WCCP
# version 3. If you're using that version of IOS, change
# this value to 3.
#
#Default:
# wccp_version 4

# TAG: wccp_incoming_address
# TAG: wccp_outgoing_address
# wccp_incoming_address Use this option if you require WCCP
# messages to be received on only one
# interface. Do NOT use this option if
# you're unsure how many interfaces you
# have, or if you know you have only one
# interface.
#
# wccp_outgoing_address Use this option if you require WCCP
# messages to be sent out on only one
# interface. Do NOT use this option if
# you're unsure how many interfaces you
# have, or if you know you have only one
# interface.
#
# The default behavior is to not bind to any specific address.
#
# NOTE, wccp_incoming_address and wccp_outgoing_address can not have
# the same value since they both use port 2048.
#
#Default:
# wccp_incoming_address 0.0.0.0
# wccp_outgoing_address 255.255.255.255

# DELAY POOL PARAMETERS (all require DELAY_POOLS compilation option)
# -----------------------------------------------------------------------------

# TAG: delay_pools
# This represents the number of delay pools to be used. For example,
# if you have one class 2 delay pool and one class 3 delays pool, you
# have a total of 2 delay pools.
#
#Default:
# delay_pools 0

# TAG: delay_class
# This defines the class of each delay pool. There must be exactly one
# delay_class line for each delay pool. For example, to define two
# delay pools, one of class 2 and one of class 3, the settings above
# and here would be:
#
#Example:
# delay_pools 2 # 2 delay pools
# delay_class 1 2 # pool 1 is a class 2 pool
# delay_class 2 3 # pool 2 is a class 3 pool
#
# The delay pool classes are:
#
# class 1 Everything is limited by a single aggregate
# bucket.
#
# class 2 Everything is limited by a single aggregate
# bucket as well as an "individual" bucket chosen
# from bits 25 through 32 of the IP address.
#
# class 3 Everything is limited by a single aggregate
# bucket as well as a "network" bucket chosen
# from bits 17 through 24 of the IP address and a
# "individual" bucket chosen from bits 17 through
# 32 of the IP address.
#
# NOTE: If an IP address is a.b.c.d
# -> bits 25 through 32 are "d"
# -> bits 17 through 24 are "c"
# -> bits 17 through 32 are "c * 256 + d"
#
#Default:
# none

# TAG: delay_access
# This is used to determine which delay pool a request falls into.
#
# delay_access is sorted per pool and the matching starts with pool 1,
# then pool 2, ..., and finally pool N. The first delay pool where the
# request is allowed is selected for the request. If it does not allow
# the request to any pool then the request is not delayed (default).
#
# For example, if you want some_big_clients in delay
# pool 1 and lotsa_little_clients in delay pool 2:
#
#Example:
# delay_access 1 allow some_big_clients
# delay_access 1 deny all
# delay_access 2 allow lotsa_little_clients
# delay_access 2 deny all
#
#Default:
# none

# TAG: delay_parameters
# This defines the parameters for a delay pool. Each delay pool has
# a number of "buckets" associated with it, as explained in the
# description of delay_class. For a class 1 delay pool, the syntax is:
#
#delay_parameters pool aggregate
#
# For a class 2 delay pool:
#
#delay_parameters pool aggregate individual
#
# For a class 3 delay pool:
#
#delay_parameters pool aggregate network individual
#
# The variables here are:
#
# pool a pool number - ie, a number between 1 and the
# number specified in delay_pools as used in
# delay_class lines.
#
# aggregate the "delay parameters" for the aggregate bucket
# (class 1, 2, 3).
#
# individual the "delay parameters" for the individual
# buckets (class 2, 3).
#
# network the "delay parameters" for the network buckets
# (class 3).
#
# A pair of delay parameters is written restore/maximum, where restore is
# the number of bytes (not bits - modem and network speeds are usually
# quoted in bits) per second placed into the bucket, and maximum is the
# maximum number of bytes which can be in the bucket at any time.
#
# For example, if delay pool number 1 is a class 2 delay pool as in the
# above example, and is being used to strictly limit each host to 64kbps
# (plus overheads), with no overall limit, the line is:
#
#delay_parameters 1 -1/-1 8000/8000
#
# Note that the figure -1 is used to represent "unlimited".
#
# And, if delay pool number 2 is a class 3 delay pool as in the above
# example, and you want to limit it to a total of 256kbps (strict limit)
# with each 8-bit network permitted 64kbps (strict limit) and each
# individual host permitted 4800bps with a bucket maximum size of 64kb
# to permit a decent web page to be downloaded at a decent speed
# (if the network is not being limited due to overuse) but slow down
# large downloads more significantly:
#
#delay_parameters 2 32000/32000 8000/8000 600/8000
#
# There must be one delay_parameters line for each delay pool.
#
#Default:
# none

# TAG: delay_initial_bucket_level (percent, 0-100)
# The initial bucket percentage is used to determine how much is put
# in each bucket when squid starts, is reconfigured, or first notices
# a host accessing it (in class 2 and class 3, individual hosts and
# networks only have buckets associated with them once they have been
# "seen" by squid).
#
#Default:
# delay_initial_bucket_level 50

# TAG: incoming_icp_average
# TAG: incoming_http_average
# TAG: incoming_dns_average
# TAG: min_icp_poll_cnt
# TAG: min_dns_poll_cnt
# TAG: min_http_poll_cnt
# Heavy voodoo here. I can't even believe you are reading this.
# Are you crazy? Don't even think about adjusting these unless
# you understand the algorithms in comm_select.c first!
#
#Default:
# incoming_icp_average 6
# incoming_http_average 4
# incoming_dns_average 4
# min_icp_poll_cnt 8
# min_dns_poll_cnt 8
# min_http_poll_cnt 8

# TAG: max_open_disk_fds
# To avoid having disk as the I/O bottleneck Squid can optionally
# bypass the on-disk cache if more than this amount of disk file
# descriptors are open.
#
# A value of 0 indicates no limit.
#
#Default:
# max_open_disk_fds 0

# TAG: offline_mode
# Enable this option and Squid will never try to validate cached
# objects.
#
#Default:
# offline_mode off

# TAG: uri_whitespace
# What to do with requests that have whitespace characters in the
# URI. Options:
#
# strip: The whitespace characters are stripped out of the URL.
# This is the behavior recommended by RFC2396.
# deny: The request is denied. The user receives an "Invalid
# Request" message.
# allow: The request is allowed and the URI is not changed. The
# whitespace characters remain in the URI. Note the
# whitespace is passed to redirector processes if they
# are in use.
# encode: The request is allowed and the whitespace characters are
# encoded according to RFC1738. This could be considered
# a violation of the HTTP/1.1
# RFC because proxies are not allowed to rewrite URI's.
# chop: The request is allowed and the URI is chopped at the
# first whitespace. This might also be considered a
# violation.
#
#Default:
# uri_whitespace strip

# TAG: broken_posts
# A list of ACL elements which, if matched, causes Squid to send
# an extra CRLF pair after the body of a PUT/POST request.
#
# Some HTTP servers has broken implementations of PUT/POST,
# and rely on an extra CRLF pair sent by some WWW clients.
#
# Quote from RFC2068 section 4.1 on this matter:
#
# Note: certain buggy HTTP/1.0 client implementations generate an
# extra CRLF's after a POST request. To restate what is explicitly
# forbidden by the BNF, an HTTP/1.1 client must not preface or follow
# a request with an extra CRLF.
#
#Example:
# acl buggy_server url_regex ^http://....
# broken_posts allow buggy_server
#
#Default:
# none

# TAG: mcast_miss_addr
# Note: This option is only available if Squid is rebuilt with the
# -DMULTICAST_MISS_STREAM option
#
# If you enable this option, every "cache miss" URL will
# be sent out on the specified multicast address.
#
# Do not enable this option unless you are are absolutely
# certain you understand what you are doing.
#
#Default:
# mcast_miss_addr 255.255.255.255

# TAG: mcast_miss_ttl
# Note: This option is only available if Squid is rebuilt with the
# -DMULTICAST_MISS_TTL option
#
# This is the time-to-live value for packets multicasted
# when multicasting off cache miss URLs is enabled. By
# default this is set to 'site scope', i.e. 16.
#
#Default:
# mcast_miss_ttl 16

# TAG: mcast_miss_port
# Note: This option is only available if Squid is rebuilt with the
# -DMULTICAST_MISS_STREAM option
#
# This is the port number to be used in conjunction with
# 'mcast_miss_addr'.
#
#Default:
# mcast_miss_port 3135

# TAG: mcast_miss_encode_key
# Note: This option is only available if Squid is rebuilt with the
# -DMULTICAST_MISS_STREAM option
#
# The URLs that are sent in the multicast miss stream are
# encrypted. This is the encryption key.
#
#Default:
# mcast_miss_encode_key XXXXXXXXXXXXXXXX

# TAG: nonhierarchical_direct
# By default, Squid will send any non-hierarchical requests
# (matching hierarchy_stoplist or not cachable request type) direct
# to origin servers.
#
# If you set this to off, Squid will prefer to send these
# requests to parents.
#
# Note that in most configurations, by turning this off you will only
# add latency to these request without any improvement in global hit
# ratio.
#
# If you are inside an firewall see never_direct instead of
# this directive.
#
#Default:
# nonhierarchical_direct on

# TAG: prefer_direct
# Normally Squid tries to use parents for most requests. If you for some
# reason like it to first try going direct and only use a parent if
# going direct fails set this to on.
#
# By combining nonhierarchical_direct off and prefer_direct on you
# can set up Squid to use a parent as a backup path if going direct
# fails.
#
# Note: If you want Squid to use parents for all requests see
# the never_direct directive. prefer_direct only modifies how Squid
# acts on cachable requests.
#
#Default:
# prefer_direct off

# TAG: strip_query_terms
# By default, Squid strips query terms from requested URLs before
# logging. This protects your user's privacy.
#
#Default:
# strip_query_terms on

# TAG: coredump_dir
# By default Squid leaves core files in the directory from where
# it was started. If you set 'coredump_dir' to a directory
# that exists, Squid will chdir() to that directory at startup
# and coredump files will be left there.
#
#Default:
# coredump_dir none
#
# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid

# TAG: redirector_bypass
# When this is 'on', a request will not go through the
# redirector if all redirectors are busy. If this is 'off'
# and the redirector queue grows too large, Squid will exit
# with a FATAL error and ask you to increase the number of
# redirectors. You should only enable this if the redirectors
# are not critical to your caching system. If you use
# redirectors for access control, and you enable this option,
# users may have access to pages they should not
# be allowed to request.
#
#Default:
# redirector_bypass off

# TAG: ignore_unknown_nameservers
# By default Squid checks that DNS responses are received
# from the same IP addresses they are sent to. If they
# don't match, Squid ignores the response and writes a warning
# message to cache.log. You can allow responses from unknown
# nameservers by setting this option to 'off'.
#
#Default:
# ignore_unknown_nameservers on

# TAG: digest_generation
# This controls whether the server will generate a Cache Digest
# of its contents. By default, Cache Digest generation is
# enabled if Squid is compiled with USE_CACHE_DIGESTS defined.
#
#Default:
# digest_generation on

# TAG: digest_bits_per_entry
# This is the number of bits of the server's Cache Digest which
# will be associated with the Digest entry for a given HTTP
# Method and URL (public key) combination. The default is 5.
#
#Default:
# digest_bits_per_entry 5

# TAG: digest_rebuild_period (seconds)
# This is the number of seconds between Cache Digest rebuilds.
#
#Default:
# digest_rebuild_period 1 hour

# TAG: digest_rewrite_period (seconds)
# This is the number of seconds between Cache Digest writes to
# disk.
#
#Default:
# digest_rewrite_period 1 hour

# TAG: digest_swapout_chunk_size (bytes)
# This is the number of bytes of the Cache Digest to write to
# disk at a time. It defaults to 4096 bytes (4KB), the Squid
# default swap page.
#
#Default:
# digest_swapout_chunk_size 4096 bytes

# TAG: digest_rebuild_chunk_percentage (percent, 0-100)
# This is the percentage of the Cache Digest to be scanned at a
# time. By default it is set to 10% of the Cache Digest.
#
#Default:
# digest_rebuild_chunk_percentage 10

# TAG: chroot
# Use this to have Squid do a chroot() while initializing. This
# also causes Squid to fully drop root privileges after
# initializing. This means, for example, that if you use a HTTP
# port less than 1024 and try to reconfigure, you will get an
# error.
#
#Default:
# none

# TAG: client_persistent_connections
# TAG: server_persistent_connections
# Persistent connection support for clients and servers. By
# default, Squid uses persistent connections (when allowed)
# with its clients and servers. You can use these options to
# disable persistent connections with clients and/or servers.
#
#Default:
# client_persistent_connections on
# server_persistent_connections on

# TAG: detect_broken_pconn
# Some servers have been found to incorrectly signal the use
# of HTTP/1.0 persistent connections even on replies not
# compatible, causing significant delays. This server problem
# has mostly been seen on redirects.
#
# By enabling this directive Squid attempts to detect such
# broken replies and automatically assume the reply is finished
# after 10 seconds timeout.
#
#Default:
# detect_broken_pconn off

# TAG: balance_on_multiple_ip
# Some load balancing servers based on round robin DNS have been
# found not to preserve user session state across requests
# to different IP addresses.
#
# By default Squid rotates IP's per request. By disabling
# this directive only connection failure triggers rotation.
#
#Default:
# balance_on_multiple_ip on

# TAG: pipeline_prefetch
# To boost the performance of pipelined requests to closer
# match that of a non-proxied environment Squid can try to fetch
# up to two requests in parallel from a pipeline.
#
# Defaults to off for bandwidth management and access logging
# reasons.
#
#Default:
# pipeline_prefetch off

# TAG: extension_methods
# Squid only knows about standardized HTTP request methods.
# You can add up to 20 additional "extension" methods here.
#
#Default:
# none

# TAG: request_entities
# Squid defaults to deny GET and HEAD requests with request entities,
# as the meaning of such requests are undefined in the HTTP standard
# even if not explicitly forbidden.
#
# Set this directive to on if you have clients which insists
# on sending request entities in GET or HEAD requests. But be warned
# that there is server software (both proxies and web servers) which
# can fail to properly process this kind of request which may make you
# vulnerable to cache pollution attacks if enabled.
#
#Default:
# request_entities off

# TAG: high_response_time_warning (msec)
# If the one-minute median response time exceeds this value,
# Squid prints a WARNING with debug level 0 to get the
# administrators attention. The value is in milliseconds.
#
#Default:
# high_response_time_warning 0

# TAG: high_page_fault_warning
# If the one-minute average page fault rate exceeds this
# value, Squid prints a WARNING with debug level 0 to get
# the administrators attention. The value is in page faults
# per second.
#
#Default:
# high_page_fault_warning 0

# TAG: high_memory_warning
# If the memory usage (as determined by mallinfo) exceeds
# value, Squid prints a WARNING with debug level 0 to get
# the administrators attention.
#
#Default:
# high_memory_warning 0

# TAG: store_dir_select_algorithm
# Set this to 'round-robin' as an alternative.
#
#Default:
# store_dir_select_algorithm least-load

# TAG: forward_log
# Note: This option is only available if Squid is rebuilt with the
# -DWIP_FWD_LOG option
#
# Logs the server-side requests.
#
# This is currently work in progress.
#
#Default:
# none

# TAG: ie_refresh on|off
# Microsoft Internet Explorer up until version 5.5 Service
# Pack 1 has an issue with transparent proxies, wherein it
# is impossible to force a refresh. Turning this on provides
# a partial fix to the problem, by causing all IMS-REFRESH
# requests from older IE versions to check the origin server
# for fresh content. This reduces hit ratio by some amount
# (~10% in my experience), but allows users to actually get
# fresh content when they want it. Note that because Squid
# cannot tell if the user is using 5.5 or 5.5SP1, the behavior
# of 5.5 is unchanged from old versions of Squid (i.e. a
# forced refresh is impossible). Newer versions of IE will,
# hopefully, continue to have the new behavior and will be
# handled based on that assumption. This option defaults to
# the old Squid behavior, which is better for hit ratios but
# worse for clients using IE, if they need to be able to
# force fresh content.
#
#Default:
# ie_refresh off

# TAG: vary_ignore_expire on|off
# Many HTTP servers supporting Vary gives such objects
# immediate expiry time with no cache-control header
# when requested by a HTTP/1.0 client. This option
# enables Squid to ignore such expiry times until
# HTTP/1.1 is fully implemented.
# WARNING: This may eventually cause some varying
# objects not intended for caching to get cached.
#
#Default:
# vary_ignore_expire off

# TAG: sleep_after_fork (microseconds)
# When this is set to a non-zero value, the main Squid process
# sleeps the specified number of microseconds after a fork()
# system call. This sleep may help the situation where your
# system reports fork() failures due to lack of (virtual)
# memory. Note, however, that if you have a lot of child
# processes, these sleep delays will add up and your
# Squid will not service requests for some amount of time
# until all the child processes have been started.
#
#Default:
# sleep_after_fork 0

# TAG: relaxed_header_parser on|off|warn
# In the default "on" setting Squid accepts certain forms
# of non-compliant HTTP messages where it is unambiguous
# what the sending application intended even if the message
# is not correctly formatted. The messages is then normalized
# to the correct form when forwarded by Squid.
#
# If set to "warn" then a warning will be emitted in cache.log
# each time such HTTP error is encountered.
#
# If set to "off" then such HTTP errors will cause the request
# or response to be rejected.
#
#Default:
# relaxed_header_parser on

# TAG: max_filedesc
# The maximum number of open file descriptors.
#
#Default:
# max_filedesc 1024

#sleep_after_fork 0
#always_direct allow abc
#always_direct allow dl2
#never_direct allow QUERY
#never_direct allow dl1
#cache_peer_access 192.168.0.253 deny dl1
#cache_peer_access 192.168.0.10 allow dl1

delay_pools 3

delay_class 1 2
delay_access 1 deny net2
delay_access 1 deny net3
delay_access 1 allow net opendl
delay_parameters 1 -1/-1 7000/7000

delay_class 2 2
delay_access 2 deny net2
delay_access 2 allow net3
delay_access 2 allow net
delay_parameters 2 -1/-1 10000/10000

delay_class 3 2
delay_access 3 allow net2
delay_parameters 3 -1/-1 -1/-1

Linux and other Free and Open Source Software

2009-12-01T16:42:00.000-08:00

Many Open source software available on internet
i have found some very useful and working links.

Linux and other Free and Open Source Software
http://www.redhat.com/software/rhel/purchase/index.html
http://www.redhat.com/software/rhel/desktop/
http://www.freesoftwarecdr.com/shop/product_info.php?products_id=135
http://www.freesoftwarecdr.com/shop/product_info.php?products_id=139
http://www.freesoftwarecdr.com/shop/product_info.php?products_id=91
http://store.mandrakesoft.com/index.php
http://www.novell.com/products/linuxprofessional/pricing.html
http://www.suse.com/us/business/products/server/sles/pricing.html
http://store.slackware.com/cgibin/
store
http://www.openbsd.com/orders.html

Customizing a GNOME Desktop of Redhat Linux

2009-11-29T10:35:00.000-08:00

Customizing a GNOME Desktop
Desktop configuration is a very personal issue, as each user seems to have a particular favored
way of doing things. Without trying some changes, however, it’s hard to know how one can do
things. You now know enough to tweak a GNOME desktop a bit; in this project, you’ll change
some commonly altered configuration settings.

Step by Step
1. From the default GNOME desktop, right-click on a blank space on the panel.
2. Click the Properties menu item.
3. You can use this page to reposition the panel to any of the four edges of the desktop, but
leave the location alone for now. In the Size drop-down menu, select Small (36 pixels).
4. Check the Show/Hide Buttons box.

5. Check the Arrows on the Hide Buttons box.
6. Click Close. The panel at the bottom of the screen should now be shorter, and its icons
smaller and more widely spaced.
7. Right-click on a blank spot on the panel and select Add To Panel.
8. Select Utility and then System Monitor. A system monitor area should appear on the panel;
it will graphically show CPU usage.
9. Right-click on a blank spot on the panel and select Launcher from the menu.
10. Select System Tools and then Terminal. A terminal icon will appear on the panel; clicking
this icon will open a terminal where you can use the command-line interface.
11. Right-click on a blank spot on the panel and select Launcher from the menu again.
12. Select the Office menu and then Project Management. A Mr. Project icon should appear on
the panel; this tool is still under development, but it is similar in concept to Microsoft Project.
13. Right-click on a blank spot on the panel and select New Panel.
14. Select the Menu Panel option, and a menu bar should appear at the top of the desktop.
Applications and actions can be invoked from this menu bar, and it can also hold additional
launchers, applets, and utilities.
15. Right-click on the new menu panel at the top of the screen.
16. Select Add To Panel, and then the Accessories menu, and the Stock Ticker option. A stock
ticker area should appear on the menu panel.
17. Right-click on the stock ticker area on the panel and select Preferences. A configuration
page should appear.
18. Type RHAT in the New Symbol field.
19. Click the Add button, and then click Close. In five minutes, the Red Hat stock price should
begin scrolling in the stock ticker area, along with the default index information.
20. Move the icons on the panels by left-clicking them and then dragging them to the desired
locations.

Exploring CUPS in Redhat Linux all linux flavors

2009-11-23T13:58:00.000-08:00

CUPS
We’ve mentioned before that CUPS was based on the Internet Printing Protocol (IPP), which it
is hoped will become a cross-platform standard for network printing. CUPS also provides
some additional advantages besides just those presented by IPP.

The designers of CUPS have gone to great lengths to make it easy to use and easy to
transition to. Administration is simplified through the use of a web-based front end to server
configuration (although third-party GUI configuration tools exist as well) and clients often
need no configuration at all. Printers are discovered automatically when possible. From the
client’s view of printing, CUPS will emulate many of the tools you’ve become used to under
lpd-style systems (or System V, if you’ve worked with that elsewhere).
CUPS introduces the concept of classes, which allow you to send a print job to a group of
printers, and have it printed on the first available machine in that group. This approach to load
balancing and failover is carried further with implicit classes, which allow multiple servers to
address the same physical printer. When two servers point to a printer of the same name, an
implicit class is automatically created with no effort required from an administrator.
Printer instances allow multiple queues to point to the same printer with slightly different
settings. This makes it really easy to choose between common features that your printer makes
available.
By using pluggable back ends for the actual output from a queue, not only is it easy to
support many types of printer hardware, but third parties can easily add support for output that
isn’t bundled in the core package. For example, Windows printing is handled by a back end
provided by the Samba team. In addition, CUPS uses a text file called a PostScript Printer
Description (PPD) to describe the features provided by a particular piece of printer hardware

Pluggable Authentication Modules (PAM)

2009-11-02T09:05:00.000-08:00

Pluggable Authentication Modules (PAM)

Programs which give privileges to users must properly authenticate each user. For instance, when you log into a system, you provide your username and password, and the log in process uses this username and password to verify your identity.

Pluggable Authentication Modules (PAM) allows the system administrator to set authentication policies for PAM-aware applications without having to recompile authentication programs. PAMdos this by utilizing a pluggable, modular architecture. Which modules PAM calls for a particular application is determined by looking at that application's PAM configuration file in the /etc/pam.d/ directory.

In most situations, you will never need to alter the default PAM configuration files for a PAM-aware application. Whenever you use RPM to install programs that require authentication, they automatically make the changes necessary to do normal password authentication using PAM. However, if you need to customize the PAM configuration file, you must understand the structure of this

Advantages of PAM
When used correctly, PAM provides the following advantages for a system administrator:

. It provides a common authentication scheme that can be used with a wide variety of applications. . It allows great fiexibility and control over authentication for both the system administrator and

application developer.
. It allows application developers to develop their program without implementing a particular authentication scheme. Instead, they can focus purely on the details of their program.

PAM Configuration Files
The directory /etc/pam.d/ contains the PAM configuration files for PAM-aware applications. In
earlier versions of PAM, the file /etc/pam.conf was used, but this file is now deprecated. The
pam.conf file is only read if the /etc/pam.d/ directory does not exist.
Each PAM-aware application or service . as applications designed to be used by many users are
commonly known . has its own file within the /etc/pam.d/ directory.
These files have a specific layout containing calls to modules usually located in the /lib/security/
directory. Additionally, each line within a PAM configuration file specifies a module type, a control
fiag, a path to the module, and, sometimes, module arguments.

PAM Service Names
Each PAM configuration file in the /etc/pam.d/ directory is named after the service for which it
controls access. It is up to the PAM-aware program to define its service name and install its PAM
configuration file in the pam.d directory. For example, the login program defines its service name
as /etc/pam.d/login.
In general, the service name is the name of the program used to access the service, not the program used to provide the service. This is why the service wu-ftpd, defines its service name as /etc/pam.d/ftp. The next four sections will describe the basic format of PAM configuration files and how they use
PAM modules to perform authentication for PAM-aware applications.

PAM Modules
There are four types of PAM modules used to control access to services. These types correlate to
different aspects of the authorization process:
. auth . These modules are used to authenticate the user by, for example, asking for and checking
a password. It can also set credentials, such as group membership or Kerberos tickets.
. account . These modules are used to make sure access is allowed. For example, it can check if
the account is expired, or it can check if the user is allowed to log in at a particular time of day.
. password. These modules are used to set passwords.
. session . These modules are used after a user has been authenticated to manage the user's
session. This module type can also perform additional tasks which are needed to allow access, like
mounting a user's home directory or making his mailbox available.

How to Install and Configure Tomcat on Linux

2009-10-30T04:48:00.000-07:00

1. First install the rpm of tomcat from tarball in /usr/local dir

cp jakarta-tomcat-5.0.24.tar.gz /usr/local /
2. tar –xzvf jakarta – tomcat-5.0.24.tar.gz
3. Make a symbolic link
ln –s /usr/local/Jakarta-tomcat-5.0.24 /usr/local/tomcat
4.Go to /etc/profile and add the lines above the following line
(export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC)
export JAVA_HOME=/usr/java/j2sdk1.4.2_05
export CATALINA_HOME=/usr/local/tomcat

5. cd /etc
6. . . /profile
7. echo $JAVA-Home
8. echo $CATALINA-HOME

Start the tomcat service by
/ usr /local/tomcat/bin /startup. Sh

Open the following file
9. pico /usr/local /tomcat/conf/tomcat- users.xml and add the following lines

()
user username = “TomcatAdmin” Password = “password”
Full Name =’” ‘role = “admin, manager , tomcat”/>

Restart the service of tomcat
/usr/local/tomcat/bin/shutdown.sh
/usr/local/tomcat/bin/startup.sh

This will authenicate the user of tomcatAdmin

2. Install the java from the cdrom
rpm –ivh java.xxxx.rpm
3. Install the mysql from cdrom
rpm –ivh mysql.xxx.rpm

You can access the mysql by sqlyog software at windows, but just writing the username “root” without any password. If you want to create some password for some user then follow the following steps

#mysql
mysql> use mysql;
Database changed

mysql> INSERT INTO user (Host, User, Password, Select_priv) VALUES ('','eis', password('pucit'), 'Y');
Query OK, 1 row affected (0.00 sec)

mysql> GRANT ALL ON hello.* TO eis;
Query OK, 0 rows affected (0.00 sec)

Now you can login by using the username “eis” with password “pucit” in sqlyoq.

4. For to use the admin of jakarta-tomcat you can , access it by
http:// ip-address:8080/admin

It will require the username and password which you have mentioned in the file
/ usr / local /tomcat/conf/tomcat- users.xml

It will open for you the administration of tomcat, you can create different websites on the same machine

5. Now insert a rule of just insert a rule of IPTABLES to redirect the PORT 8080 of tomcat to PORT 80 of HTTP

iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j REDIRECT --to-port 8080

6. For to use the mysql just start its service
/etc/init.d/mysql start
7. You can restart the tomcat service as
/usr/local/tomcat/bin/shutdown.sh
/usr/local/tomcat/bin/startup.sh

8. Now you can access your website
http://www.domainname.com

What is and How Work Linux Transparent Proxy

2009-10-27T10:35:00.000-07:00

What is it?

Transparent Proxy is away that proxies connections without client

noticing. This means that if you browse to www.yahoo.com when this request

reachs your gateway it will be re-directed to another port where a proxy

service like squid will be active. The client thinks that it's exchanging

data with remote host but in the reality it's just exchanging data with the

gateway.

How can I support it?

To support Transparent Proxy once more you'll have to re-compile your

kernel this time the main features to support are:

Networking Options -->

(...)

[*] IP: firewalling

[*] IP: Transparent Proxy support

(...)

Of course you'll probably enable mascarade on your host, to know which

options have to be enabled check the IP masquerade section.

Configuring

-----------

Finally to make Transparent Proxy work you have to add a redirection

action on ipchains just simply giving the command:

root@ExampleBox: ~# /sbin/ipchains -A input -p TCP --dport 80 -s

192.168.0.0/24 -j REDIRECT 8080

Problems with Linux Booting into the Graphical Installation

2009-10-17T10:41:00.000-07:00

Problems with Booting into the Graphical Installation
There are some video cards that will not work properly with the Red Hat Linux installation program.
The end result will be a problem booting into the graphical installation program.
If the installation program will not run using its default settings, it will try to run in a lower resolution
mode. If that still fails, the installation program will run in text mode.
Users who have video cards that will not run at 800 x 600 resolution should type lowres at the
boot: prompt to run the installation program in 640 x 480 resolution.

How to Add NEw User in Linux

2009-10-17T03:04:00.001-07:00

Required steps:
– Edit the /etc/passwd file to define the user's account.
– Set an initial password.
– Create the user's home directory.
• Extra steps (optional):
– Copy default startup files to the user's home directory.
– Add the user to the /etc/group file.
– Set the user's mail home and establish mail aliases.
– Enter the user in the site-wide user database (NIS).
– Configure disk quotas.
– Verify that the account is set up correctly.
– Record accounting information.

Linux 5 Disk Druid's Buttons

2009-10-14T11:23:00.000-07:00

Disk Druid's Buttons
These buttons control Disk Druid's actions. They are used to change the
attributes of a partition (for example the file system type and mount point) and
also to create RAID devices. Buttons on this screen are also used to accept the
changes you have made, or to exit Disk Druid. For further explanation, take a
look at each button in order:
New: Used to request a new partition. When selected, a dialog box appears
containing fields (such as the mount point and size fields) that must be filled in.
Edit: Used to modify attributes of the partition currently selected in the
Partitions section.
Selecting Edit opens a dialog box. Some or all of the fields can be edited,
depending on whether the partition information has already been written to disk.
You can also edit free space as represented in the graphical display to create a
new partition within that space. Either highlight the free space and then select
the Edit button, or double-click on the free space to edit it.
To make a RAID device, you must first create (or reuse existing) software
RAID partitions. Once you have created two or more software RAID partitions,
select Make RAID to join the software RAID partitions into a RAID device.
Delete: Used to remove the partition currently highlighted in the Current
Disk Partitions section. You will be asked to confirm the deletion of any
partition.
Reset: Used to restore Disk Druid to its original state. All changes made
will be lost if you Reset the partitions.
RAID: Used to provide redundancy to any or all disk partitions. It should
only be used if you have experience using RAID. To read more about RAID,
refer to the Red Hat Enterprise Linux Deployment Guide.
To make a RAID device, you must first create software RAID partitions. Once
you have created two or more software RAID partitions, select RAID to join the
software RAID partitions into a RAID device.

LVM: Allows you to create an LVM logical volume. The role of LVM
Logical Volume Manager) is to present a simple logical view of underlying
physical storage space, such as a hard drive(s). LVM manages individual
physical disks — or to be more precise, the individual partitions present on
them. It should only be used if you have experience using LVM. To read more
about LVM, refer to the Red Hat Enterprise Linux Deployment Guide. Note,
LVM is only available in the graphical installation program.
To create an LVM logical volume, you must first create partitions of type
physical volume (LVM). Once you have created one or more physical volume
LVM) partitions, select LVM to create an LVM logical volume.

What is Routing Metrics

2009-10-06T03:19:00.000-07:00

Routing Metrics
Routing tables contain information used by switching software to select the best route. But how,
specifically, are routing tables built? What is the specific nature of the information they contain?
How do routing algorithms determine that one route is preferable to others?
Routing algorithms have used many different metrics to determine the best route. Sophisticated
routing algorithms can base route selection on multiple metrics, combining them in a single (hybrid)
metric. All the following metrics have been used:
Path Length
Reliability
Delay
Bandwidth
Load
Communication Cost

Path length is the most common routing metric. Some routing protocols allow network
administrators to assign arbitrary costs to each network link. In this case, path length is the sum of the costs associated with each link traversed. Other routing protocols define hop count, a metric that specifies the number of passes through internetworking products, such as routers, that a packet must take en route from a source to a destination.
Reliability, in the context of routing algorithms, refers to the dependability (usually described in
terms of the bit-error rate) of each network link. Some network links might go down more often than others. After a network fails, certain network links might be repaired more easily or more quickly than other links. Any reliability factors can be taken into account in the assignment of the reliability ratings, which are arbitrary numeric values usually assigned to network links by network administrators. Routing delay refers to the length of time required to move a packet from source to destination through the internetwork. Delay depends on many factors, including the bandwidth of intermediate network links, the port queues at each router along the way, network congestion on all intermediate network links, and the physical distance to be travelled. Because delay is a conglomeration of several important variables, it is a common and useful metric. Bandwidth refers to the available traffic capacity of a link. All other things being equal, a 10-Mbps Ethernet link would be preferable to a 64-kbps leased line. Although bandwidth is a rating of the maximum attainable throughput on a link, routes through links with greater bandwidth do not necessarily provide better routes than routes through slower links. If, for example, a faster link is busier, the actual time required to send a packet to the destination could be greater. Load refers to the degree to which a network resource, such as a router, is busy. Load can be calculated in a variety of ways, including CPU utilization and packets processed per second. Monitoring these parameters on a continual basis can be resource-intensive itself.
Communication cost is another important metric, especially because some companies may not care about performance as much as they care about operating expenditures. Even though line delay may be longer, they will send packets over their own lines rather than through the public lines that cost money for usage time.

linux service chkconfig rc.local Linux Listing Services

2009-09-16T10:34:00.000-07:00

Chkconfig show you which linux services start in linux startu up.
linux start different service on diferent runlevels.

#chkconfig --list

if you want to start any service in linux startup there is many ways to
load or start service in startup

1) chkconfig
2) rc.local

chkconfig
Only run this command in one time when you install new server like squid dns or dhcp.
there is 7 run levels in linux. 3 is command prompt and 5 is graphic interface run level

chkconfig --level 35 squid on
chkconfig --level 35 named on
chkconfig --level 35 dhcpd on

this is start up script file, jus add these lines or add any command in
this start up script, and also you can add the iptables command's in rc.local files.

rc.local
service named start
service squid start
service dhcpd start

How to start and stop Linux services squid dns dhcp

2009-09-16T10:27:00.000-07:00

Manually starting and stopping service
We can manually start and stop service
/etc/rc.d/init.d/smb stop
/etc/rc.d/init.d/smb restart
/etc/rc.d/init.d/named restart
/etc/rc.d/init.d/squid restart
/etc/rc.d/init.d/dhcpd restart
/etc/rc.d/init.d/iptabels restart

SOme other way to stop or start or restart service

Squid
serivce squid restar (Stop and Start the Squid service)
service squid stop (Stop the Squid Services)
service squid start (Start Squid Services)

IPtabels
serivce iptables restar (Stop and Start the Squid service)
service iptables stop (Stop the Squid Services)
service iptables start (Start Squid Services)

DNS
serivce named restar (Stop and Start the Squid service)
service named stop (Stop the Squid Services)
service named start (Start Squid Services)

DHCPD
serivce dhcpd restar (Stop and Start the Squid service)
service dhcpd stop (Stop the Squid Services)
service dhcpd start (Start Squid Services)

Linux Backup and Recovery how to use tar command

2009-09-11T12:44:00.000-07:00

Using tar Command in almost all Linux Flavour's

The tar command is most often used to archive files. Its
command syntax is
where optionsis the list of commands and options for tar, and
filesis the list of files to add or extract from the archive.

For example, the command
# tar options files
# tar cvf backup.tar /etc

# tar cvf backup.tar /etc
packs all of the files in /etc into the tar archive backup.tar.
The first argument to tar, “cvf”
c tells tar to create a new archive file.

v forces tar to use verbose mode, printing each file name as it is
archived.

f option tells tar that the next argument, backup.tar, is the
name of the archive to create.

The rest of the arguments to tar are the file and directory names
to add to the archive.

# tar xvf backup.tar
Will extract the tar file backup.tar in the current directory.
Old files with the same name are overwritten when extracting files
into an existing directory.
Remember!!!
Before extracting tar files it is important to know where the files
should be unpacked.

# tar tvf backup.tar
can be used to display a listing of the archive's files without
extracting them.
You can see what directory the files in the archive are stored
relative to, and extract the archive in the correct location.

how to run or execute chm files in linux

2009-09-10T10:58:00.000-07:00

how to execute chm files in linux

download the following rpms on ur pc:-
http://dag.wieers.com/packages/chmlib/chmlib-0.35-1.1.fc3.rf.i386.rpm ftp://rpmfind.net/linux/dag/fedora/3/en/i386/dag/RPMS/wxGTK-2.4.2-5.1.fc3.rf.i386.rpm http://acmserver.cs.ucr.edu/%7Ensoracco/rpms/xchm-0.9.8-1.i386.rpm

and also install them in the same sequence. using the command:-
rpm -ivh
Note:- i am giving the path of packages for fedora cpre 3. if want for any other os take a look at the following sites.
chmlib:-
http://dag.wieers.com/packages/chmlib/
wxGTK:- ftp://rpmfind.net/linux/dag/xchm: -
platform independent for all redhat's

Rotecting yourself Linux from being a spam base

2009-09-01T10:28:00.000-07:00

Rotecting yourself from being a spam base

Sendmail allows for someone to telnet to port 25 and do an expn (expand) to see what users and aliases are on your machine. Also, vrfy (verify) means someone can get legal e-mail addresses from your box and send spam through your machine.
Don't want that, so look in your /etc/sendmail.cf file for a line that looks like this:

################ Options ################
Now cut and paste these next few lines below that:
# turning off the expand option and requiring a helo from# a remote computerOpnoexpn,novrfy,needmailhelo
Now there is no expansion, no verify, and sendmail requires a helo with a legitimate DNS in order to use the mailer.
Then look in your /etc/mail/aliases file and ensure you have only your own boxen and/or subnet in there as OK or RELAY. That will help cut down on spammers' ability to find relay machines to do their dirty work for them.

Linux Tips & Tricks Speed up your Hard Drive

2009-09-01T10:03:00.000-07:00

Speeding up your hard drive

Get faster file transfer by using 32-bit transfers on your hard drive
Just add the line:
hdparm -c3 /dev/hdX
to a bootup script.

If you use SuSE or other distros based on SYS V,
/sbin/init.d/boot.localshould work for you.

This enables 32-bit transfer on your hard drive. On some systems it can improve transfer performance by 75%.

To test your performance gain, type:
hdparm -t -T /dev/hdX

What is a default gateway? What happens if I don't have one? Linux

2009-08-29T01:01:00.000-07:00

What is a default gateway? What happens if I don't have one?
a gateway is a routing device that knows how to pass traffic between different subnets and
networks. A computer will know some routes (a route is the address of each node a packet
must go through on the Internet to reach a specific destination), but not the routes to every
address on the Internet. It won't even know all the routes on the nearest subnets. A gateway
will not have this information either, but will at least know the addresses of other gateways it
can hand the traffic off to. Your default gateway is on the same subnet as your computer, and
is the gateway your computer relies on when it doesn't know how to route traffic.
The default gateway is typically very similar to your IP address, in that many of the numbers
may be the same. However, the default gateway is not your IP address. To see what default
gateway you are using, follow the steps below for your operating system.

Why Share a Common Structure?

2009-08-24T02:54:00.000-07:00

Why Share a Common Structure?
An operating system's le system structure is its most basic level of organization. Almost all of the ways an operating system interacts with its users, applications, and security model are dependent upon the way it stores its files on a storage device. It is crucial for a variety of reasons that users, as well as
programs, be able to refer to a common guideline to know where to read and write files. A file system can be seen in terms of two different logical categories of files:

Shareable vs. unshareable files
Variable vs. static files

Shareable files are those that can be accessed by various hosts; unshareable files are not available to any other hosts. Variable files can change at any time without any intervention; static
files, such as
read-only documentation and binaries, do not change without an action from the system administrator
or an agent that the system administrator has placed in motion to accomplish that task. The reason for looking at files in this way is to help you understand the type of permissions given to the directory that holds them. The way in which the operating system and its users need to use the files
determines the directory where those files should be placed, whether the directory is mounted readonly or read-write, and the level of access allowed on each file. The top level of this organization is crucial, as the access to the underlying directories can be restricted or security problems may manifest
themselves if the top level is left disorganized or without a widely-used structure. However, simply having a structure does not mean very much unless it is a standard. Competing structures can actually cause more problems than they x. Because of this, Red Hat has chosen the
the most widely-used file system structure and extended it only slightly to accommodate special files used within Red Hat Linux.

What Is Linux Swap Space why we need Linux Swap Partition

2009-08-10T10:47:00.000-07:00

What is Swap Space?
Swap space in Linux is used when the amount of physical memory (RAM) is full. If the system needs more memory resources and the physical memory is full, inactive pages in memory are moved to the swap space. While swap space can help machines with a small amount of RAM, it should not be considered a replacement for more RAM. Swap space is located on hard drives, which have a slower access time than physical memory.
Swap space can be a dedicated swap partition (recommended), a swap le, or a combination of swap partitions and swap les. The size of your swap space should be equal to twice your computer's RAM, or 32 MB, whichever amount is larger, but no more than 2048 MB (or 2 GB).

Advance Linux Permission Common Umask Setting

2009-08-07T10:43:00.000-07:00

Common umask settings and their effects:
umask User Access Group Access Other
0000 all all all
0002 all all read, execute
0007 all all none
0022 all read, execute read, execute
0027 all read, execute none
0077 all none none

Now setuid and setgid

2009-08-07T10:41:00.000-07:00

Now setuid and setgid

Sometimes, unprivileged users must be able to accomplish tasks that require
privileges. An example is the passwd program, which allows you to change your
password. Changing a user's password requires modifying the password field in the
/etc/passwd file. However, you should not give a user access to change this file
directly- the user could change everybody else's password as well! Likewise, the mail
program requires that you be able to insert a message into the mailbox of another
user, yet you should not to give one user unrestricted access to another's mailbox.
To get around these problems, linux allows programs to be implemented with special
privileges. Processes executing these programs can assume another UID or GID

when they're running. A program that changes its UID is called a SUID program (set-
UID); a program that changes its GID is called a SGID program (set-GID). A
program can be both SUID and SGID at the same time.
When a SUID program is run, its effective UID becomes that of the owner of the file,
rather than of the user who is running it.
If setuid permission is applied on a file like :
[root@mainserver / ]# chmod 4511 myprogram.sh
then myprogram.sh has the ownership and permissions as :
-r-s--x--x 1 root admin 16336 Feb 14 2003 myprogram.sh
,then this means that whenever any user, like kamran logs on to the system and runs
this program then this program is run as not user kamran but user root !!!!. The “ s ”
in the owner's permission set indicates that this file has setuid bit on.
If setgid permission is applied on a file like :
[root@mainserver / ]# chmod 2711 myprogram.sh
then myprogram.sh has the ownership and permissions as :
-rwx--s--x 1 root admin 16336 Feb 14 2003 myprogram.sh
,then this means that any process that executes this SGID program has its effective
GID changed to the program's GID (admin in this case). Files created by the process
can have their primary group set to this GID as well, depending on the permissions of
the directory in which the files are created. The “ s ”in the group permission set
indicates that this file has setgid bit on.
The setgid bit is normally useful on directories. For example you have a directory
named newproject and it has ownership as root:students and permissions like:

[root@mainserver / ]# chmod 2770 myprogram.sh
[root@mainserver / ]# ls -l
drwxrws--- 2 root students 4096 Jul 13 21:38 newproject
This means that any user who creates an object within this directory will effectively
create that object with students in the group ownership.
In other words, the SGID bit on a directory controls the way that groups are assigned
for files created in the directory. If the SGID bit is set, files created in the directory
have the same group as the directory if the process creating the file also is in that
group. Otherwise, if the SGID bit is not set, or if the process is not in the same group,
files created inside the directory have the same group as the user's effective group ID
(usually the primary group ID).
Setuid and setgid can be security risk you can find files which have setuid and setgid
set on them by:
[root@mainserver / ]# find / $-perm -004000 -o -perm -002000 $
 -type f -print
This find command starts in the root directory (/) and looks for all files that match
mode 002000 (SGID) or mode 004000 (SUID). The -type f option causes the search
to be restricted to files. The -print option causes the name of every matching file to
be printed.
Note that if you are using NFS, you should execute find commands only on your file
servers. You should further restrict the find command so that it does not try to search
networked disks. Otherwise, use of this command may cause an excessive amount of
NFS traffic on your network. To restrict your find command, use the following:
[root@mainserver / ]# find / $ -local -o -prune $
 $ -perm -004000 -o -perm -002000 $ type f -print

How to Setuid, setgid and sticky bit:

2009-08-07T10:38:00.000-07:00

Setuid, setgid and sticky bit
Till now you have used three octal numbers for permissions for three types of users,
i.e. Owner, group and others. These three octal numbers / digits have values from

000 till 777 , representing: “no permissions to any one” till “all permissions for
everyone”, respectively. There are in fact four octal number positions designed for
file and directory permissions. The fourth number happens to be on the left side of any permission set, and if not present, then is assumed to be 0 (zero). This number can be 1 or 2 or 4 maximum and it's special meaning are below:

1 Sticky bit
2 Set group ID on execution
4 Set user ID on execution

Now first sticky bit :
If sticky bit permission is applied on a file like :
[root@mainserver / ]# chmod 1755 myfile.txt
, then as per the man page:
“On older Unix systems, the sticky bit caused executable files to be
hoarded in swap space. This feature is not useful on modern VM
systems, and the Linux kernel ignores the sticky bit on files. Other kernels
may use the sticky bit on files for system-defined purposes. On
some systems, only the superuser can set the sticky bit on files.”
What this means is that sticky bit on files is useless in linux.
Sticky bit on a file can be checked by the ls command. The “ T ” indicates that this file has sticky bit on.

[root@mainserver / ]# ls -l
-rw-r--r-T 1 root root 4847 Jul 8 12:26 myfile.txt
And if sticky bit is implemented on a directory like:
[root@mainserver / ]# chmod 1777 mydirectory
, then as per the man page:
“When the sticky bit is set on a directory, files in that directory may
be unlinked or renamed only by root or their owner. Without the sticky
bit, anyone able to write to the directory can delete or rename files.
The sticky bit is commonly found on directories, such as /tmp, that are
world-writable.”
What this means is that sticky bit on a directory allows users to create files in that
directory with a facility that only root or the user who created the file will be able to
delete or rename the file.
Sticky bit on a directory can be checked by the ls command. The “ t ” indicates that
this file has sticky bit on. A common example is the /tmp directory on Linux.
[root@mainserver / ]# ls -l
drwxrwxrwt 21 root root 4096 Jul 13 17:39 tmp

Linux Runlevels

2009-08-04T10:21:00.000-07:00

Before you can congure access to services, you must understand Linux runlevels. A runlevel is a
state, or mode, that is dened by the services listed in the directory /etc/rc.d/rc
1 x
2 .d, where
3 x
4
is the number of the runlevel.
Red Hat Linux uses the following runlevels:

. 0 . Halt
. 1 . Single-user mode
. 2 . Not used (user-denable)
. 3 . Full multi-user mode
. 4 . Not used (user-denable)
. 5 . Full multi-user mode (with an X-based login screen)
. 6 . Reboot

If you congured the X Window System during the Red Hat Linux installation program, you had the option of choosing a graphical or text login screen. If you chose a text login screen, you are operating in runlevel

Booting Linux Single-User Mode

2009-08-04T10:17:00.001-07:00

Booting Single-User Mode
You may be able to boot single-user mode directly. If your system boots, but does not allow you to log in when it has completed booting, try single-user mode.
If you are using GRUB, use the following steps to boot into single-user mode:

1. If you have a GRUB password congured, type p and enter the password.
2. Select Red Hat Linux with the version of the kernel that you wish to boot and type e for edit.
You will be presented with a list of items in the conguration le for the title you just selected.
3. Select the line that starts with kernel and type e to edit the line.
4. Go to the end of the line and type single as a separate word (press the [Spacebar] and then
type single). Press [Enter] to exit edit mode.
5. Back at the GRUB screen, type b to boot into single user mode.

If you are using LILO, specify one of these options at the LILO boot prompt (if you are using the
graphical LILO, you must press [Ctrl]-[x] to exit the graphical screen and go to the boot: prompt):
boot: linux single
boot: linux emergency
In single-user mode, your computer boots to runlevel 1. Your local lesystems will be mounted, but
your network will not be activated. You will have a usable system maintenance shell.

In emergency mode, you are booted into the most minimal environment possible. The root lesystem will be mounted read-only and almost nothing will be set up. The main advantage of emergency mode over linux single is that your init les are not loaded. If init is corrupted or not working, you can still mount lesystems to recover data that could be lost during a re-installation.
Have you ever rebuilt a kernel and, eager to try out your new handiwork, rebooted before running /sbin/lilo? If you did not have an entry for an older kernel in lilo.conf, you had a problem. If you would like to know a solution to this problem, read this section.
In many cases, you can boot your Red Hat Linux system from the Red Hat Linux boot disk 1 with your root lesystem mounted and ready to go. Here is how to do it:

Enter the following command at the boot disk's boot: prompt:
linux single root=/dev/hdXX initrd=
Replace the XX in /dev/hdXX with the appropriate letter and number for your root partition.
What does this command do? First, it starts the boot process in single-user mode, with the root partition set to your root partition. The empty initrd specication bypasses the installation-related image on the boot disk, which will cause you to enter single-user mode immediately.
Is there a negative side to using this technique? Unfortunately, yes. Because the kernel on the Red Hat Linux boot disk only has support for IDE built-in, if your system is SCSI-based, you will not be able to do this. In that case, you will have to access rescue mode using the linux rescue command mentioned above.

How to, Stop porn for God's sake Using Squid Proxy Server

2009-07-31T01:09:00.000-07:00

Stop porn for God's sake:
If you want to restrict users so that they are denied access to certain sites, like porn
sites, etc. Then you can make an acl for bad sites put all the possible words which are
normally part of url of those bad sites, in a text file with each word at separate line.
Create and block the acl as follows in the squid.conf file:
acl badsites url_regex -i "/etc/squid/badsites.txt"
http_access deny badsites
It should be noted that the placement of http_access lines are very important in
SQUID's expected behavior. You need to deny badsites BEFORE allowing the
http_access to your client src acl.
Your configuration with blocked sites would look like this:
acl badsites url_regex -i "/etc/squid/badsites.txt"
acl mynet src 192.168.1.0/24
http_access deny badsites
http_access allow mynet
http_access allow localhost
http_access deny all
Your badistes file should contain all words on separate lines which you want to be
search in the URL and then blocked by SQUID. An example badsites.txt file is
below:
sex
xxx
movies
This is quite effective approach. You may need to watch your
/var/log/squid/access.log for such sites and add those names to this file.

Common problems while joining a Linux SAMBA domain from win2k

2009-07-27T10:38:00.000-07:00

1) "The account used is a computer account. Use your global user account or
local user account to access the server".
This problem comes with Windows 2000 machines with service pack 2. Solution is
to create a machine account for each win2k computer on the SAMBA computer.
Another solution is to try changing the windows computer's machine name from
Network properties, but this seldom works (depends on the mood of win 2000
machine).

2) "The credentials supplied conflict with an existing set of credentials".
This is a problem on windows client side.. Windows will not let you connect as two
different users to the same share on the remote computer. To over come this problem,
log out of the windows computer (restart if it doesn't behave) , then again log in first
as local administrator and then supply the root login and it's samba generated
password while joining the domain.

3) "The domain SMBDOMAIN could not be contacted".
Check your SMB configuration. Check for presence of machine accounts (including
the group machines) and their SMB passwords. Check the network settings of
windows. Restart the windows computer. Should work.
Now something about plain text passwords :
In the Samba configurations above, we are using encrypted passwords. But if for any
reason, for example, incompatibility of samba encrypted passwords and windows
encrypted passwords, we can configure both sides to use plain text passwords. On
samba side, we will just put a remark on the following two lines in the smb.conf
file
#encrypt password = yes
#smb passwd file = /etc/samba/smbpasswd
And on windows side we have to edit the registry and enable plain text password
support. The procedure is different for win 9x, windows NT and windows 2000.

Scenario 3 SMB Samba server as domain controller

2009-07-27T10:33:00.000-07:00

Scenario 3 SMB Samba server as domain controller
SAMBA server will be configured on our machine
mainserver.mydomain.com. The workgroup name can be same as the domain
name already being used in the current windows setup (provided the NT server for
the domain is off line), BUT it should never be of the name name as your DNS
domain name. We will create a new workgroup named SAMBADOMAIN on SAMBA
machine (the server), and configure the windows clients to be a part of this domain.
(Confusing? Well, on a SAMBA machine,
in /etc/samba/smb.conf, the word workgroup serves for workgroup as well
as domain for windows computers).
Server side configuration:
1) Modify the /etc/samba/smb.conf file and give the following entries:
[root@mainserver /]# vi /etc/samba/smb.conf
[global]
workgroup = SAMBADOMAIN
comment = samba server on the local lan placed in the
server room
hosts allow = 192.168.1. 192.168.2. 127.
security = user
load printers = yes
encrypt password = yes
smb passwd file = /etc/samba/smbpasswd
domain logons = yes
os level = 64
preferred master = yes
domain master = yes
wins support = yes
[homes]
comment = home directories of users
read only = no
create mask = 0750
browseable = no
[netlogon]
comment = SAMBA network logon services for microsoft
clients
path = /users/netlogon
guest ok = yes
browseable = no
locking = no
[cdrom]

comment = CDROM on SAMBA server
path = /mnt/cdrom
read only = yes
browseable = yes
public = yes
[floppy]
comment = Floppy drive on SAMBA server
path = /mnt/floppy
read only = no
browseable = yes
valid users = @students ; note that the group students exists in
/etc/groups
[linuxproject]
comment = project on linux by MS 4 students
path = /users/ms4/linuxproject
read only = no
browseable = yes
valid users = nayyar, inam
Note: All paths defined in the smb.conf file must exist. If they don’t create them
yourself. Also if you are going to use clients of Windows 98 and onwards or
Windows NT service pack 3 or higher, then these systems use encrypted passwords
by default. We need to provide either encrypted password support in SAMBA server
or modify the registry of the windows computers and enable plain text passwords in
them.
To enable support for encrypted passwords in the SAMBA server, perform the
following steps:
a. Create a separate password file for Samba. To create one based on your
existing /etc/passwd file, at a shell prompt, type the following command:
[root@mainserver /]# cat /etc/passwd mksmbpasswd.sh > /etc/samba/smbpasswd
The mksmbpasswd.sh script is installed in your /usr/bin directory with the
samba package.
b. Use the following command to change permissions on the Samba password
file so that only root has read and write permissions:
[root@mainserver /]# chmod 600 /etc/samba/smbpasswd

c. The script does not copy user passwords to the new file. To set each Samba
user’s password, use the command smbpasswd username(replace username
with each user’s username). A Samba user account will not be active until a Samba
password is set for it.
[root@mainserver /]# smbpasswd -a inam
d. The next step is to enable encrypted passwords in the Samba configuration
file. In the file smb.conf, uncomment the following lines:
encrypt password = yes
smb passwd file = /etc/samba/smbpasswd
2) Test your smb.conf file by running testparm command which is only
available for SAMBA. This command should show all the shares without any errors.
[root@mainserver /]# testparm
3) If the above command works fine then run the smb services now by:
[root@mainserver /]# /etc/rc.d/init.d/smb start
Notes:
Windows NT 4 :
At present, Samba needs to have a *nix account for every entry in the 'smbpasswd'
file, so this means that each Windows NT4/2000computer needs a *nix account on
the Domain Controller. Machine accounts are differentiated from user accounts by
appending a $ to the end of the machine's name. For Windows NT clients, you can
create these accounts manually. To make a domain machine account, issue the
following commands on the samba Domain Controller as 'root':
Create the group "machines" by:
[root@mainserver /]# groupadd machines
[root@mainserver /]# useradd -d /dev/null -g machines -c 'Machine Account'
 -s /bin/false -M $
[root@mainserver /]# smbpasswd -am

e.g. To add a machine account of a machine win98 on the samba server, you would
use:
[root@mainserver /]# groupadd machines
[root@mainserver /]# useradd -d /dev/null -g machines -c 'Machine Account' -s
 /bin/false -M win98$
[root@mainserver /]# smbpasswd -am win98
Windows 2000/XP :
Windows 2000 is different than NT. As far as NT is concerned, while joining the
domain, you are given an option to create a computer account in the domain server.
This allows machine accounts to be made on the fly. At the moment the only user
that can create computer accounts automatically is root. This means we must first
make a samba password for 'root' with:
[root@mainserver /]# smbpasswd -a root
It is recommended that you use a different password than real Linux password for
root for security reasons. To make a domain machine account, issue the following
commands on the Domain Controller as 'root':
[root@mainserver /]# groupadd machines
[root@mainserver /]# useradd -d /dev/null -g machines -c 'Machine Account'
 -s /bin/false -M win2k$
[root@mainserver /]# smbpasswd -am win2k
Optionally in order to make the computer accounts on the fly while joining the
domain, you need the following entry in the smb.conf file.
add user script = /usr/sbin/useradd -d /dev/null -g machines
 -c 'Machine account' -s /bin/false -M %u
Note the absence of $ in this script, SAMBA automatically adds the $ for you when
it is configured as domain log on server. Also the group machines was already
created manually. This also works for Windows XP.
The above solution specifically solves the problem when you are joining the
Windows 2000 workstation to a samba domain and you get the following error:
"The account used is a computer account. Use your global user account or local
user account to access the server". This problem comes with Windows 2000

machines with service pack 2. Another solution is to try changing the windows
computer's machine name from Network properties, but this seldom works (depends
on the mood of win 2000 machine).
Client side configuration:
On the client side, i.e. on the computer having Microsoft Windows, open the network
neighborhood properties, and in the identification tab, type in SAMBADOMAIN in
the DOMAIN textbox. Also set the other network related properties, e.g. IP
addresses, address of DNS and name of Primary WINS server which is the IP
address of SAMBA server. Press ok and restart the windows machine. Once
restarted, type in any user name and password of the user defined on SAMBA server
and select the domain SAMBADOMAIN in the drop down list. You will be greeted
after a pause of 10 to 30 seconds. Restart and log on to the new domain with the user
name inam, lets say. Now you should be able to see the SAMBA server in the
Network Neighborhood window. Double click it, and you should be able to see the
shares: inam, cdrom, floppy and linuxproject. On double clicking on the share
linuxproject you should be able to see the contents of this share. You will be asked
for the password if you logged on as someone else other than inam or nayyar, this
will be the password of one of the users nayyar or inam (as shown above), which are
defined in the machine running SAMBA. Similarly password of one of the users in
the group students (defined in SAMBA machine) may be required once accessing the
share floppy. To assign a drive letter to a share, you can either right click on the
share and select Map to drive. Or you can use the command on the windows DOS
shell prompt:
C:\> net use F: \\mainserver.mydomain.com\cdrom

Scenario2 workgroup model, shares on linux machine

2009-07-26T02:45:00.000-07:00

Scenario2 (workgroup model, shares on linux machine):
SAMBA server will be configured on our machine
mainserver.mydomain.com. The workgroup name can be same as the one

already being used in the current windows setup. However, we will create a new
workgroup named SAMBAWORKGROUP and configure the windows clients to be a
part of this workgroup.
Server side configuration:
1) Modify the /etc/samba/smb.conf file and give the following entries:
[root@mainserver /]# vi /etc/samba/smb.conf
[global]
workgroup = SAMBAWORKGROUP
comment = samba server on the local lan placed in the server room
hosts allow = 192.168.1. 192.168.2. 127.
security = user
load printers = yes
os level = 64
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
preferred master = yes
domain master = yes
wins support = yes
[cdrom]
comment = CDROM on SAMBA server
path = /mnt/cdrom
read only = yes
browseable = yes
public = yes
[floppy]
comment = Floppy drive on SAMBA server
path = /mnt/floppy
read only = no
browseable = yes
valid users = @students ; note that the group students exists in /etc/groups
[linuxproject]
comment = project on linux by MS 4 students
path = /users/ms4/linuxproject
read only = no
browseable = yes
valid users = nayyar, inam
Note: All paths defined in the smb.conf file must exist. If they don’t create them
yourself.
2) Test your smb.conf file by running testparm command which is only
available for SAMBA. This command should show all the shares without any errors.
[root@mainserver /]# testparm less
3) If the above command works fine then run the smb services now by:

[root@mainserver /]# /etc/rc.d/init.d/smb start
4) Create users inam and nayyar ( on the local linux machine, if not already created )
and generate SMB passwords for them which will be used to access the shares
defined on this computer from the windows client. Use the following commands to
generate SMB passwords:
[root@mainserver /]# cat /etc/passwd mksmbpasswd.sh > /etc/samba/smbpasswd
[root@mainserver /]# smbpasswd -a inam
[root@mainserver /]# smbpasswd -a nayyar
Note: The first command in step 4 needs to be given once.

Client side configuration:
On the client side, i.e. on the computer having Microsoft Windows, open the network
neighborhood properties, and in the identification tab, type in SAMBAWORKGROUP in
the workgroup text box. Also set the other network related properties, e.g. IP
addresses, address of DNS and name of Primary WINS server which is the IP
address of SAMBA server. Press OK and restart the windows machine. Once
restarted, type in user name inam and his password. You will be logged on. Now
you should be able to see the SAMBA server in the Network Neighborhood window.
Double click it, and you should be able to see the shares: inam, cdrom,
floppy and linuxproject. If you did not log in as a regular linux user, then on
double clicking on the SAMBA server will give you a login screen, here again you
have a chance to provide a regular linux user account and it's samba password. If still
you do not supply a regular login and you just press OK, then you will be presented
with the shares on the server without the share inam displayed. In fact you will be
logged in as user nobody , and this will be a lot restrictive access than assumed.
To assign a drive letter to a share, you can either right click on the share and select
Map network drive. Or you can use the command on the windows DOS shell
prompt:
C:\> net use F: \\mainserver.mydomain.com\cdrom

Samba Configuration with Windows Computer in Domain Model

2009-07-25T02:26:00.000-07:00

SAMBA
SAMBA is derived from SMB, which stands for Session Message Block. It is a
protocol used to exchange data between windows and *nix computers. SMB was
built on Microsoft's NetBIOS protocol, which can be run over TCP/IP.
Packages:

samba-a.b (server side)
samba-client-a.b (client side)
samba-common-a.b (client server both)

Scenario:
In fact there will be three scenarios.
1. Accessing shares on windows computers from *nix computers
2. Providing access to shares on the SAMBA server to users logging on from
Windows computers, in a work-group model
3. Providing access to shares and logon authentication to users logging on from

Windows computers, in a Domain model

Scenario1

(workgroup model, shares on windows machine):
We have some share (ebooks) available on windows computer
(wks1.mydomain.com) and want to access them from a linux machine.
Windows side configuration:
Nothing special, just enable sharing on the directories / folders you want to share.

Optionally set permissions of these shares.
Linux side configuration:
There is no configuration required. Only the commands smbclient and
smbmount will be used to access the windows machine. So the related packages
must already be installed on the client side.
To see the list of shares available on the windows computer:
[root@mainserver /]# smbclient -L wks1.mydomain.com

Just press enter on the password prompt and you would be given a list of shares
available on this computer.

Note: In case of windows 2000 / xp , simple pressing enter will not do the trick. You
will be denied access to list of shares in this way. In order to see a list of shares on a
windows 2000/xp, you need to specify a valid username already defined and enabled
on the windows 2000/xp machine. When asked for password, you have to supply the
password of that user. In case of a guest account, which is normally available and
enabled on a windows network, you can use guest and a blank password with it:

[root@mainserver /]# smbclient -L wks1 -U guest
To connect to the share ebooks on the windows machine, with a windows user
kamran, use:

[root@mainserver /]# smbclient //wks1/ebooks -U kamran

If you see the smb:\> prompt, you have successfully logged in.
If you don’t use the -U switch then the username and password of
the currently logged in linux user will be sent to the windows machine, which may
get rejected. So it is better to use the username and password of the user already
created on the windows machine you are connecting to.
Once you are logged in, type help for a list of commands. Like FTP client, you can
use get or mget and put or mput commands to copy files from and to the
windows computer respectively. To exit smbclient, type quit at the

smb:\>
prompt.

If you want, you can mount the remote windows share ebooks on some local
mount point on your machine, say /mnt/work . Do do so, use:

[root@mainserver /]# smbmount //wks1/ebooks /mnt/work -o username=kamran
or
[root@mainserver /]# mount -t smbfs //wks1/ebooks /mnt/work -o username=kamran

Linux User Managemenet and File Permission Ownerships

2009-07-24T11:17:00.000-07:00

User Management and file permissions / ownerships :
To add a new group called mailusers use:
[root@mainserver /]# groupadd mailusers
To add new user kamran and make him a member of the group mailusers, use:
[root@mainserver /]# useradd -s /bin/false -g mailusers kamran
To change the password if some user, say kamran, run the following command as
root:
[root@mainserver /]# passwd kamran
To lock the password of user kamran, run the following command as root:
[root@mainserver /]# passwd -l kamran
To un-lock the password of user kamran, run the following command as root:
[root@mainserver /]# passwd -u kamran

To delete a user say kamran, including his home directory, use:
[root@mainserver /]# userdel -r kamran
To change permissions of an object (file or directory), use chmod:
[root@mainserver /]# chmod 770 myfile.txt
(changes the permissions of the file to rwx for both owner and group)
or
[root@mainserver /]# chmod ug+rwx,o-rwx myfile.txt
To change ownership of a directory /project to kamran and set the group
permissions to the group mailusers, use chown (-R will change ownership of all files
and subdirectories under the directory project:
[root@mainserver /]# chown –R kamran:mailusers /project
For more topics like sudo, umask and setgid, etc, see the chapter, Advance
permissions
Modules management :
To insert a module, eg. you want to add the support for your 3com Ethernet card
3c509 ,then use :
[root@mainserver /]# modprobe 3c509 io=0x300 irq=5
or
[root@mainserver /]# insmod 3c509 io=0x300 irq=5
then
[root@mainserver /]# ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up
To list the currently loaded modules use :

[root@mainserver /]# lsmod
To remove a module use :
[root@mainserver /]# rmmod 3c509

Server Load Balancing: Basic Concepts

2009-07-21T02:36:00.000-07:00

Server Load Balancing: Basic Concepts

Server load balancing is not a new concept in the server world. Several clustering technologies were invented to perform collaborative computing, but succeeded only in a few proprietary systems. However, load balancers have emerged as a powerful solution for mainstream applications to address several areas, including server farm scalability, availability, security, and manageability. First and foremost, load balancing dramatically improves the scalability of an application or server farm by distributing the load across multiple servers. Second, load balancing improves availability because it is able to direct the traffic to alternate servers if a server or application fails. Third, load balancing improves manageability in several ways by allowing network and server administrators to move an application from one server to another or to add more servers to run the application on the fly. Last, but not least, load balancers improve security by protecting the server farms against multiple forms of denial−of−service (DoS) attacks.
The advent of the Internet has given rise to a whole set of new applications or services: Web, DNS, FTP, SMTP, and so on. Fortunately, dividing the task of processing Internet traffic is relatively easy. Because the Internet consists of a number of clients requesting a particular service and each client can be identified by an IP address, it’s relatively easy to distribute the load across multiple servers that provide the same service or run the same application.
This chapter introduces the basic concepts of server load balancing, and covers several fundamental concepts that are key to understanding how load balancers work. While load balancers can be used with several different applications, load balancers are often deployed to manage Web servers. Although, we will use Web servers as an example to discuss and understand load balancing, all of these concepts can be applied to many other applications as well.

Using Standard DNS for load balancing

2009-07-17T00:59:00.000-07:00

Using Standard DNS for load balancing

DNS can be used for load balancing across multiple servers using the standard round−robin mechanism available in the DNS servers. Each IP address configured for the domain name may actually be a VIP on a load balancer that’s bound to several servers connected to the load balancer. DNS can be used for some rudimentary load balancing across the various individual servers or multiple load balancers at different sites where each load balancer performs server load balancing.

But the DNS has no knowledge of which of the different IP addresses is actually working or how much load is on each one of those sites. A site may be completely inaccessible, but the DNS may continue to provide that IP address as part of its reply. We can’t view this as a shortcoming of the DNS architecture because DNS was never designed for GSLB. It was devised as a way to provide the name−to−address translation.

Local DNS Caching

2009-07-17T00:58:00.000-07:00

Local DNS Caching
Once the local DNS receives the reply, it will cache that information for a specified time, known as time to live (TTL). TTL is specified by the authoritative DNS as part of its reply. That means, the local DNS will simply reply to all subsequent requests with the information it has from the earlier DNS reply until the TTL expires. Once the TTL expires, the next request to the local DNS will trigger a request to the authoritative DNS again. Caching helps ensure faster response time for the same name to address resolution queries from subsequent clients. At the same time, TTL helps ensure that the local DNS captures any updates or changes from the authoritative DNS. Changing the TTL to a lower value causes the local DNS to query the authoritative DNS more often. Changing the TTL to a higher value puts the local DNS at the risk of having
stale information for increased durations.
If the local DNS receives multiple IP addresses as part of the DNS reply, it may give one IP address to each of its clients in a round−robin manner. In addition to the local DNS caching the DNS responses, the client browser also caches the DNS response. Unfortunately, popular client browsers currently ignore the TTL set by the authoritative DNS. Versions 3.x of Microsoft Internet Explorer, for example, cache the DNS response for 24 hours. Unless the browser
application is terminated and restarted, it does not query the DNS again for 24 hours for a given domain.
Versions 4.x and later cache the DNS response for 30 minutes. Microsoft provides a note on the support section of its Web site on how to change the cache time−out value for Internet Explorer by modifying certain entries in the registry. (Search for keywords ie cache dns timeout in the support section of Microsoft’s Web site.)

Blog Advertising is better then popup ads

2009-07-16T11:04:00.000-07:00

Blogging is better then Popup adds

This is internet word almost 40% people of every use internet for different purpose. In marketing work many way to promote your product or your company in the market. People use different methods for advertising there is some of examples of marketing.

Affiliate Marketing

Ezine Marketing

BLOGGING

E-Book Marketing

Network Marketing

Google Ads

Web Marketing

As you see on internet many commercial web sites use different method’s for adds. The one method popup adds people don’t like such as www.funmaza.com and lot pop up adds that adds just time taking of people.

The Blog Advertising is best and good way of advertising. Infect presently peoples like to read and write blog’s. And the paid blogging make charm in blogging word. Some of people like to write blog by profession some of write to blog by hobbies. Blogs troche the mental thinking of peoples and solve the people problems. Actually you can say blogs help the humanities because the blog (People) solve the many problems of poples most of student get more benefits from blogging for preparing the assignments. Students also can get the advantage of Paid blogging.

Linux Zip and Unzip

2009-07-16T02:51:00.000-07:00

Zip and Unzip
To compress a le with zip, type the following command:

zip -r filename.zip filesdir

In this example, filename.zip represents the le you are creating and filesdir represents the
directory you want to put in the new zip le. The -r option species that you want to include all les
contained in the filesdir directory recursively.
To extract the contents of a zip le, type the following command:

unzip filename.zip

You can use zip to compress multiple les and directories at the same time by listing them with a
space between each one:

zip -r filename.zip file1 file2 file3 /usr/work/school

The above command compresses file1, file2, file3, and the contents of the
/usr/work/school directory (assuming this directory exists) and places them in a le named

filename.zip

Gzip and Gunzip

2009-07-16T02:49:00.000-07:00

Gzip and Gunzip
To use gzip to compress a le, type the following command at a shell prompt:
gzip filename
The le will be compressed and saved as filename.gz.
To expand the compressed le, type the following command:

gunzip filename.gz

The filename.gz is deleted and replaced with filename.
You can use gzip to compress multiple les and directories at the same time by listing them with a
space between each one:

gzip -r filename.gz file1 file2 file3 /usr/work/school

The above command compresses file1, file2, file3, and the contents of the
/usr/work/school directory (assuming this directory exists) and places them in a le named

filename.gz.

A Typical KDE Desktop

2009-07-16T02:47:00.000-07:00

A Typical KDE Desktop
The KDE desktop displays application launchers, document windows, le folders, and so on. You can also access the main menu and congure the desktop to suit your needs.

The long bar across the bottom of the desktop is the panel. The panel contains application launchers, status indicators, and the desktop manager. You can have up to 16 desktops running at the same time in KDE. The panel taskbar shows your currently running applications.

Icons located on the desktop can be les, folders, device links, or application launchers. Click on an icon to open the associated resource. The KDE desktop works similarly to other graphical desktop environments. You can drag and drop
les and application icons to any location on the desktop. You can also add new icons for all types of applications and resources to the desktop, panel, or le manager. The desktop itself is also highly customizable. You can change the appearance of buttons, window and frame decorations, and backgrounds easily. Conguration tools are also available which allow you to customize the way the desktop behaves at events such as single- and double-clicking mouse buttons and combining (also called chording) keystrokes to create time-saving shortcuts.
The default KDE desktop displays icons for the trash can, your home directory, the KDE Control Panel, and a link to the Red Hat website. You can access any one of these resources by clicking on the associated icon.

When you right-click on these icons, you will see several options for working with these resources, such as Delete Rename Move to Trash, and Copy. You can drag and drop unwanted items such as les you no longer need to the Trash icon. Right-click on the trashcan and select Empty Trash Bin to delete the items from your system permanently.

FORWARD and NAT Rules

2009-07-13T05:04:00.000-07:00

FORWARD and NAT Rules
Most organizations are allotted a limited number of publicly routable IP addresses from their ISP. Due to this limited allowance, administrators must nd creative ways to share access to Internet services without giving scarce IP addresses to every node on the LAN. Using class C private IP address is the common way to allow all nodes on a LAN to properly access network services internally and externally. Edge routers (such as rewalls) can receive incoming transmissions from the Internet and route the bits to the intended LAN node; at the same time, it can also route outgoing requests from a LAN node to the remote Internet service. This forwarding of network trafc can become dangerous at times, especially with the availability of modern cracking tools that can spoof internal IP addresses and make the remote attacker's machine act as a node on your LAN. To prevent this, iptables provides routing and forwarding policies that you can implement to prevent aberrant usage of network resources.

The FORWARD policy allows an administrator to control where packets can be routed. For example, to allow forwarding for an entire internal IP address range, the following rule can be set:

iptables -A FORWARD -i eth1 -j ACCEPT

By default, IPv4 policy in Red Hat Linux kernels disables support for IP forwarding, which prevents boxes running Red Hat Linux from functioning as dedicated edge routers. To enable IP forwarding, run the following command or place it in your rewall initialization script:

echo "1" > /proc/sys/net/ipv4/ip_forward

FORWARD rules can be implemented to restrict certain types of trafc to the LAN only, such as local network le shares through NFS or Samba. The following rules reject outside connections to Samba shares:

iptables -A FORWARD -p tcp --sport 137:139 -j DROP
iptables -A FORWARD -p udp --sport 137:139 -j DROP

To take the restrictions a step further, you can block all outside connections that attempt to spoof private IP address ranges to inltrate your LAN. If a LAN uses the 192.168.1.0/24 range, a rule can set the Internet facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range. Because it is recommended to reject forwarded packets as a default
policy, any other spoofed IP address will be rejected automatically.

iptables -A FORWARD -p tcp -s 192.168.1.0/24 -i eth0 -j DROP
iptables -A FORWARD -p udp -s 192.168.1.0/24 -i eth0 -j DROP

Rules can also be set to route trafc to certain machines, such as a dedicated HTTP or FTP server, preferably one that is isolated from the internal network on a DMZ. To set a rule for routing all incoming HTTP requests to a dedicated HTTP server at IP address 10.0.4.2 and port 80 (outside of the 192.168.1.0/24 range of the LAN), network address translation (NAT) calls a PREROUTING table to forward the packets to the proper destination ( the \ denotes a continuation of a one-line command):

iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 10.0.4.2:80

With this command, all HTTP connections to port 80 from the outside of the LAN will be routed to the HTTP server on a separate network from the rest of the internal network. This form of network segmentation can prove safer than allowing HTTP connections to a machine on the network.

Linux Unix Sudu Usage

2009-07-11T13:30:00.000-07:00

Sudo :
Best explanation is the man page itself:
“sudo allows a permitted user to execute a command as the superuser or another user, as specified in the sudoers file. The real and effective uid and gid are set to match those of the target user as specified in the passwd file (the group vector is also initialized when the target
user is not root). By default, sudo requires that users authenticate themselves with a password (NOTE: by default this is the user’s pass- word, not the root password). Once a user has been authenticated, a timestamp is updated and the user may then use sudo without a password
for a short period of time (5 minutes unless overridden in sudoers).
sudo determines who is an authorized user by consulting the file /etc/sudoers. By giving sudo the -v flag a user can update the time stamp without running a command. The password prompt itself will also time out if the user’s password is not entered within 5 minutes (unless
overridden via sudoers).”
What this says is that sudo is used / can be used, by administrator (root ), to grant
execute permissions to specific users. For example, users can be granted to execute
the mount command, which is by default only executable by root. The benefit of
using sudo is that you don't have to mess with the setuid or setgid bits of the target
program, e.g. Mount . Rather you just mention the user or group in the
/etc/sudoers file and that is it. Users can use sudo command along mount
command to get their work done.
The /etc/sudoers file is quite easy to understand. But remember you have to
edit it NOT with vi. You have to use visudo command.
[root@mainserver / ]# visudo
Assume you want to give cdrom mount and unmount ability to the group named
students along the ability to shutdown the local machine.
You would add the following lines to the /etc/sudoers file.
[root@mainserver / ]# visudo
%students ALL=/bin/mount /dev/cdrom,/bin/umount /mnt/cdrom
%students localhost=/sbin/shutdown -h now
Now the users (members of group students) would use the sudo command to mount
various file systems.
[root@mainserver / ]# sudo mount /dev/cdrom /mnt/cdrom
[root@mainserver / ]#

Linux Unix Umask

2009-07-11T13:27:00.000-07:00

Umask :
The umask (UNIX shorthand for "user file-creation mode mask") is a four-digit octal number that UNIX uses to determine the file permission for newly created files.
Every process has its own umask, inherited from its parent process.
The umask specifies the permissions you do not want given by default to newly
created files and directories. umask works by doing a bitwise AND with the bitwise complement of the umask. Bits that are set in the umask correspond to permissions that are not automatically assigned to newly created files.
By default, most UNIX versions specify an octal mode of 666 (any user can read or write the file) when they create new files. Likewise, new programs are created with a mode of 777 (any user can read, write, or execute the program).
The most common umask values are 022, 027, and 077. A umask value of 022 lets the owner both read and write all newly created files, but everybody else can only read them:
0666 default file-creation mode
(0022) umask
0644 resultant mode
A umask value of 077 lets only the file's owner read all newly created files:
0666 default file-creation mode
(0077) umask
0600 resultant mode
A simple way to calculate umask values is to remember that the number 2 in the
umask turns off write permission, while 7 turns off read, write, and execute
permission.

A umask value of 002 is commonly used by people who are working on group
projects. If you create a file with your umask set to 002, anyone in the file's group will be able to read or modify the file. Everybody else will only be allowed to read it:
0666 default file-creation mode
(0002) umask
0664 resultant mode
On many UNIX systems, the default umask is 022. This is inherited from the init
process, as all processes are descendants of init. Some systems may be configured to use another umask value, or a different value may be set in the startup files.
The designers of these systems chose this umask value to foster sharing, an open computing environment, and cooperation among users. Most prototype user accounts shipped with UNIX operating systems specify 022 as the default umask, and many computer centers use this umask when they set up new accounts. Unfortunately, system administrators frequently do not make a point of explaining the umask to novice users, and many users are not aware that most of the files they create are readable by every other user on the system.
A recent trend among computing centers has been to set up new accounts with a
umask of 077, so a user's files will, by default, be unreadable by anyone else on the system unless the user makes a conscious choice to make them readable.
Common umask settings and their effects:
umask User Access Group Access Other
0000 all all all
0002 all all read, execute
0007 all all none
0022 all read, execute read, execute
0027 all read, execute none
0077 all none none

Migrating to Open Source 90% Less than Upgrading Microsoft

2009-07-10T13:43:00.000-07:00

Migrating to Open Source 90% Less than Upgrading Microsoft
To tide us over until that more comprehensive analysis is undertaken, we have found a recently released independent study by the Dutch government. In that report10, the researchers found that migrating to an open source desktop productivity platform was 90% less expensive than migrating to the new version of the Microsoft productivity platform.
This included accounting for all the costs of migration, such as retraining,
redevelopment of macros and addon applications, any conversion costs for existing documents etc. As this is only a single data point, it would be impossible to rely on the results as a template for all Microsofttoopen source migrations. However, it is independent research, undertaken by a public sector organisation which has no vested interest in either Microsoft's nor Linux's position in this matter. This research was also based on a large scale migration, involving over 2000 desktops. Certainly within the realm of organisational size we are considering in this TCO, There is another important point to consider when modelling your organisation's cost of upgrading to a newer version of Microsoft products versus the cost of migrating to Linux and open source. Most rganisations will likely factor in the costs associated with a single upgradeversusmigration cycle. By this we mean an organisation calculating the cost of upgrading to the next version of the Microsoft product versus migrating to Linux, rather than including the subsequent upgrades as well.
Many of the costs of upgrading to newer versions of Microsoft platforms (licences,
software assurance etc.) have to be borne again and again. Most of the costs of migrating to Linux are borne once, during the initial migration. Any subsequent upgrades for that Linux platform occur with no licence costs nor software assurance costs. Therefore, to provide a more realistic appraisal and model of this scenario, you should include two or three full refresh lifecycles, stretching over a period of 510 years. Therefore rather than an upgrade versus migration, you contrast costs of an upgradeupgradeupgrade versus migrationupgradeupgrade
process.

LILO and the x86 Boot Process

2009-07-08T09:34:00.000-07:00

This section will discuss in more detail the specic role LILO plays when booting an x86 system. For
a detailed look at the overall boot process, see Section 3.2.
LILO loads itself into memory almost identically to GRUB, except it is only a two stage loader.
1. The Stage 1 or primary boot loader is read into memory by the BIOS from the MBR2. The
primary boot loader exists on less than 512 bytes of disk space within the MBR. The only thing
it does is load the Stage 2 boot loader and pass to it disk geometry information.
2. The Stage 2 or secondary boot loader is read into memory. The secondary boot loader displays
the Red Hat Linux initial screen. This screen allows you to select which operating system or
Linux kernel to boot.
3. The Stage 2 boot loader reads the operating system or kernel and initrd into memory. Once LILO determines which operating system to start, it loads it into memory and hands control of the machine to that operating system.
Once the Stage 2 boot loader is in memory, LILO displays the initial Red Hat Linux screen with the different operating systems or kernels it has been congured to boot. If you only have Red Hat Linux installed and have not changed anything in LILO's conguration le, you will see only linux as an option. If you install SMP kernel support, you will see linux-up as an option. If you have set up LILO
to boot other operating systems as well, this screen is your chance to select what operating system will boot. Use your arrow keys to highlight the operating system and press If you would like to have a command prompt to enter a command to LILO, press [Ctrl]-[X]. LILO
displays a LILO: prompt on the screen and waits for input from the user.

Linux Virtual File System

2009-07-08T09:19:00.000-07:00

Under Linux, all data are stored as les. Most users are familiar with the two primary types of les:
text and binary. But the /proc/ directory contains another type of le called a virtual le. It is for this reason that /proc/ is often referred to as a virtual le system.
These virtual les have unique qualities. Most of them are listed as zero bytes in size and yet when one is viewed, it can contain a large amount of information. In addition, most of the time and date settings on virtual les reect the current time and date, indicative of the fact they constantly changing.
Virtual les such as interrupts, /proc/meminfo, /proc/mounts, and /proc/partitions provide an up-to-the-moment glimpse of the system's hardware. Others, like /proc/filesystems and the /proc/sys/ directory provide system conguration information and interfaces.
For organizational purposes, les containing information on a similar topic are grouped into virtual directories and sub-directories. For instance, /proc/ide/ contains information for all physical IDE devices. Likewise, process directories contain information about each running process on the system.

Salaries and Services Costs Microsoft and Linux

2009-07-05T10:48:00.000-07:00

Network Infrastructure Specification and Costs
Network Infrastructure is calculated as the cost of equipping one computer, whether it be a
workstation or a server, with a connection point on a port or a switch, appropriate cabling
and a wall socket, as per current industry bestpractice.
Research has shown this turns out
to be approximately $100 per computer.
Therefore, network infrastructure is calculated as the number of computers multiplied by
$100.
Total Cost of Network Infrastructure 259 x $100 = $25,900.00
Staff Salary Specifications and Costs
Staff for both our Windows platform model and our Linux/Open Source environment were
sourced from online placement agency firms (such as Dice.com and Mojolin.com). We
performed a search using some of the core technologies required for both platforms, and
itemised three core staff members for our example organisation. We require a Senior
systems administrator and coordinator,
reporting to our example firm's executive
management. We also require a midlevel
generalist, and a junior helpdesk
support
staffer. Ancillary or specialist technical services will be provided by external consultants.
Windows Platform Permanent Staff
Salary for Senior Systems Admin @ $66,000.00 perannum
for 3 years = $198,000.00
Salary for Midlevel
Systems Admin @ $46,000.00 perannum
for 3 years =
$138,000.00
Salary for Junior Support Admin @ $36,000.00 perannum
for 3 years = $108,000.00
Total Cost of Windows Platform Permanent Staff = $444,000
Linux Platform Permanent Staff
Salary for Senior Systems Admin @ $71,000.00 perannum
for 3 years = $213,000.00
Salary for Midlevel
Systems Admin @ $49,000.00 perannum
for 3 years =
$147,000.00
Salary for Junior Support Admin @ $38,000.00 perannum
for 3 years = $114,000.00
Total Cost of Linux Platform Permanent Staff = $474,000
Specialist Consultancy Services
Most organisations need specialist external IT consultancy services and the same applies
for our example organisation. Previously we have allocated the same funds for sourcing
All text material Copyright © 2002, 2004 Cybersource® Pty. Ltd. (http://www.cybersource.com.au/).
All trademarks are the property of their respective trademark holders. Document Build: 291 Page 35 of 44
external consultants for both Windows and Linux, but this time we have allocated three
times as much to the Linux consultancy in order to respond to feedback we received from
the first version of this document.
Total Cost of Specialist Windows Consultancy Services = $45,000
Total Cost of Specialist Linux Consultancy Services = $135,000
Training
We will allocate US$30,000 for training for our organisation's staff over the lifetime of
this TCO model. With this budget allocation, they will be trained for increased
competence in either of the Microsoft Windows or Linux open source platforms by
commensurate commercial training firms.
Total Cost of Training $30,000

Linux Vs Microsoft Windows Comparison

2009-07-04T13:21:00.000-07:00

Windows Platform Solution
For our Windows platform solution, we have selected the following operating systems,
backoffice technologies and office productivity tools.
Product Price (USD) Supplier Comments

Symantec AntiVirus Corporate Edition $37.90
Symantec Price is per license when ordered in quantities of 100 to 250.
Windows Server 2003 $3,999.00
Microsoft 32bit Enterprise, includes 25 CALs
Microsoft Internet Information Server (web server)
Free Microsoft Bundled with Windows 2003 Server.
Microsoft Commerce Server 2002 $19,999.00/CPU Microsoft Price is for enterprise edition.
Requires Microsoft SQL.
Microsoft ISA 2004 $1,499.00/CPU Microsoft Standard edition.
Enterprise edition not yet available.

Microsoft SQL Server $19,999.00/CPU Microsoft Retail price for Enterprise version.
Despite the price, this is actually cheaper than a server and CAL based solution.

Microsoft Exchange 2003 $3,999.00 plus $67.00/CAL
Microsoft Requires Windows 2003 Server.

Enterprise edition. Microsoft Visual Studio .Net 2003 $2,499.00

Microsoft Enterprise Architect version. Windows XP Professional $299.00 (per user) Microsoft
Microsoft Office Standard $399.00

Linux Platform Standard Solution
For our standard Linux platform solution, we have selected the following open source
backoffice technologies and office productivity tools.
Product Price (USD) Comments Linux boxed sets (options)
Linux distributions suitable for being servers and workstations.
Only one copy needed. Where possible prices have been obtained from the distributor.
Alternatively, you can download many of these for free from the Internet.

Debian 3.0 (stable) $16.99 18
Fedora Core 2 $15.99 19
Mandrake 10.0 Bundle $84.90
Slackware 10.0 $39.95
SuSE 9.1 Professional $89.95
Apache (web server) Included with Linux distributions or free download. An efficient and extensible web
server used on more than 67% of the Internet.20
Squid (proxy server) Included with Linux distributions or free download.
MySQL or PostgreSQL Included with Linux distributions or free download.
IPTables (firewall) IPTables included with Linux distributions or free download.
State and packet based filtering.
PF provides greater functionality (including traffic shaping).
Sendmail or Postfix (mail server)
Included with Linux distributions or free download.
KDevelop (IDE) Included with Linux distributions or free download.
GIMP (graphics) Included with Linux distributions or free download.
OpenOffice (productivitysuite)
Included with Linux distributions or free download.
Standard file formats include Star, Open & Microsoft Office files, plus can generate PDF files.
OSCommerce (ecommercesystem)
Available from: http://oscommerce.com

Disabling Shutdown Via Ctrl-Alt-Del

2009-07-03T06:45:00.000-07:00

By default, /etc/inittab species that your system is set to shutdown and reboot the system in
response to a [Ctrl]-[Alt]-[Del] key combination used at the console. If you would like to completely disable this ability, you will need to comment out the following line in /etc/inittab by putting a hash mark (#) in front of it:ca::ctrlaltdel:/sbin/shutdown -t3 -r now Alternatively, you may just want to allow certain non-root users the right to shutdown the system from the console using [Ctrl]-[Alt]-[Del]. You can restrict this privilege to certain users, by taking the following steps: 1. Add a -a option to the /etc/inittab line shown above, so that it reads: ca::ctrlaltdel:/sbin/shutdown -a -t3 -r now The -a ag tells shutdown to look for the /etc/shutdown.allow le, which you will create in the next step. 2. Create a le named shutdown.allow in /etc. The shutdown.allow le should list the usernames of any users who are allowed to shutdown the system using [Ctrl]-[Alt]-[Del].

The format of the /etc/shutdown.allow le is a list of usernames, one per line, like the following: stephen jack sophie According to this example shutdown.allow le, stephen, jack, and sophie are allowed to shutdown the system from the console using [Ctrl]-[Alt]-[Del]. When that key combination is used, the shutdown -a in /etc/inittab checks to see if any of the users in /etc/shutdown.allow (or root) are logged in on a virtual console. If one of them is, the shutdown of the system will continue; if not, an error message will be written to the system console instead. For more information on shutdown.allow see the shutdown man page.

Adding a Novell NetWare (NCP) Printer

2009-07-03T06:42:00.000-07:00

To add a Novell NetWare (NCP) printer, click the New button in the main Printer Conguration
Tool window. The window shown in Figure 26-1 will appear. Click Next to proceed.
You will see the screen shown in Figure 26-9. Enter a unique name for the printer in the Queue Name text eld. The printer name cannot contain spaces and must begin with a letter a through z or A through Z. The valid characters are a through z, A through Z, 0 through 9, -, and _.
Select Novell Printer from the Queue Type menu, and click Next.

Booting Rescue Mode

2009-07-02T07:38:00.000-07:00

To boot your system in rescue mode, boot from a Red Hat Linux boot disk or the Red Hat Linux
CD-ROM #1, and enter the following command at the installation boot prompt:
boot: linux rescue You can get to the installation boot prompt in one of these ways:
. By booting your system from an installation boot diskette made from the boot.img image. This
method requires that the Red Hat Linux CD-ROM #1 be inserted as the rescue image or that the
rescue image be on the hard drive as an ISO image. 1
. By booting your system from the Red Hat Linux CD-ROM #1.
. By booting from a network disk made from the bootnet.img or PCMCIA boot disk made from
pcmcia.img. You can only do this if your network connection is working. You will need to identify
the network host and transfer type. For an explanation of how to specify this information, refer to the Ofcial Red Hat Linux Installation Guide.
After booting off a boot disk or Red Hat Linux CD-ROM #1 and providing a valid rescue image, you
will see the following message:
The rescue environment will now attempt to find your Red Hat
Linux installation and mount it under the directory
/mnt/sysimage. You can then make any changes required to your
system. If you want to proceed with this step choose
'Continue'. You can also choose to mount your filesystem
read-only instead of read-write by choosing 'Read-only'.
If for some reason this process fails you can choose 'Skip'
and this step will be skipped and you will go directly to a
command shell.
If you select Continue, it will attempt to mount your lesystem under the directory /mnt/sysimage.
If it fails to mount a partition, it will notify you. If you select Read-Only, it will attempt to mount
your lesystem under the directory /mnt/sysimage, but in read-only mode. If you select Skip, your
lesystem will not be mounted. Choose Skip if you think your lesystem is corrupted.
Once you have your system in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2
(use the [Ctrl]-[Alt]-[F1] key combination to access VC 1 and [Ctrl]-[Alt]-[F2] to access VC 2):
sh-2.05a#
If you selected Continue to mount your partitions automatically and they were mounted successfully,
you are in single-user mode.
To mount a Linux partition manually inside rescue mode, create a directory such as /foo, and type the following command:
mount -t ext3 /dev/hda5 /foo
In the above command, /foo is a directory that you have created and /dev/hda5 is the partition you want to mount. If the partition is of type ext2, replace ext3 with ext2.
If you do not know the names of your partitions, use the following command to list them:
fdisk -l

Unable to Boot Linux

2009-07-02T07:37:00.000-07:00

This problem is often caused by the installation of another operating system after you have installed Red Hat Linux. Some other operating systems assume that you have no other operating systems on your computer, and they overwrite the Master Boot Record (MBR) that originally contained the GRUB or LILO boot loader. If the boot loader is overwritten in this manner, you will not be able to boot Red Hat Linux unless you can get into rescue mode.
Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation and it changes the order of your partitions. If the partition number of your / partition changes, the boot loader will not be able to nd it to mount the partition. To x this problem, boot in rescue mode and modify /boot/grub/grub.conf if you are using GRUB or /etc/lilo.conf if you are using LILO.

How to Establishing a Wireless Connection

2009-07-01T06:19:00.000-07:00

Wireless Ethernet devices are becoming increasingly popular. The conguration is similar to the Ethernet conguration except that it allows you to congure ESSID, mode, frequency, channel, transmit rate, and key for your wireless device.

To add a wireless Ethernet connection, follow these steps:
1. Click the Devices tab.
2. Click the Add button.
3. Select Wireless connection from the Device Type list, and click Forward.
4. If you have already added the wireless network interface card to the hardware list, select it from the Ethernet card list. Otherwise, select Other Ethernet Card to add the hardware device.

5. If you selected Other Ethernet Card, the Select Ethernet Adapter window appears. Select
the manufacturer and model of the Ethernet card and the device. If this is the rst Ethernet card
for the system, select eth0, if this is the second Ethernet card for the system, select eth1, and so
on. The Network Administration Tool also allows the user to congure the resources for the
wireless network interface card. Click Forward to continue.
6. On the Congure Wireless Connection page as shown in Figure 11-12, congure the ESSID,
mode, frequency, channel, transmit rate, and key for your wireless device.

7. On the Congure Network Settings page, choose between DHCP and static IP address. You
may specify a hostname for the device. If the device receives a dynamic IP address each time
the network is started, do not specify a hostname. Click Forward to continue.
8. Click Apply on the Create Wireless Device page.

Web Directories

2009-07-01T06:18:00.000-07:00

Web Directories is changing the face of marketing. Web Directories enabled the open dialogue between companies and consumers. Before engaging in web directories companies need to explore the various options available and decide which methods will likely have the greatest impact on their target audience.

Things need when you build new web directory
1. Web Directory Design & Layout
2. Keyword Research
3. Link Building
4. Autoresponders
5. Visitor Analysis

Before joining the web directories you have to focus your business objective & marketing strategy. When you search what is the marketing media for your business promotion. First of all look at web directories. If you choose web directories you will get better result instead of other marketing media’s.

Web directories are the best sources to combine the different type of business under one roof. Jasminedirectory.com, Maxdirectory.eu, Yahoo web directories and Twd Web Directory are the example of this roof. Choose the web directory which have variety of business category and also have many links. If you want to promote your business on national (Country Level) choose the same country web directory like you live in Pakistan than use HamariWeb Directory.

Web directories are kind of relationship marketing, relationship marketing Acquiring, Maintaining and Retaining Customers. Web directory is the example of business Marketing Relationships (BMR).

NFS Mount Options

2009-07-01T02:22:00.000-07:00

Beyond mounting a le system via NFS on a remote host, a number of different options may be
specied at the time of the mount that can make it easier to use. These options can be used with
manual mount commands, /etc/fstab settings, and autofs, and other mounting methods.
The following options are the most popular for NFS mounts:
. hard or soft . species whether the program using a le via an NFS connection should stop
and wait (hard) for the server to come back online if the host serving the exported le system is
unavailable, or if it should report an error (soft).
If you specify hard, you will not be able to terminate the process waiting for the NFS communication
to resume unless you also specify the intr option.
If you specify soft, you can set an additional timeo=
ç
value
è
option, where
ç
value
è
species
the number of seconds to pass before the error is reported.
. intr. allows NFS requests to be interrupted if the server goes down or cannot be reached.
. nolock . is occasionally required when connecting to older NFS server. To require locking, use
the lock option.
. noexec . does not permit the execution of binaries on the mounted le system. This is useful if
your Red Hat Linux system is mounting a non-Linux le system via NFS that contains binaries that
will not execute on your machine.
. nosuid. does not allow set-user-identier or set-group-identier bits to take effect.
. rsize=8192 and wsize=8192.may speed up NFS communication for reads (rsize) and writes
(wsize) by setting a larger data block size, in bytes, to be transferred at one time. Be careful when
changing these values; some older Linux kernels and network cards may not work well with larger
block sizes.
. nfsvers=2 or nfsvers=3. specify which version of the NFS protocol to use.
Many more options are listed on the mount man page, including options for mounting non-NFS le
systems.

Why We Use Web Directories?

2009-06-29T12:22:00.001-07:00

Web Directories is the Best way to promot your Business in the whole world. In the Advertising Filed every one wants to save money and time. When we advertising our business on “Web Directories” and free web directories are the answer. Free web directories are a great place to promote your web site, and your product promotion to your valuable clients.

The Web directories like a force in the internet and can give your website extreme boost on internet. Many new web directories are not know by the mass users of the internet, but this is likely to change as the web directory becomes a respected and highly visited site.

Many new web directories do not require a back link which is great thing for building up web presence and search engine ranking recently Google and the other major search engines have edited their algorithms as to not place as much emphasis n reciprocal links. The Web directory can become full with hundreds of sites advertising on a single page.

Changing Permissions (chmod)

2009-06-29T02:00:00.000-07:00

The access rights for any given file can be modified by using
the change mode (chmod) command.

To change the access rights
You must specify the following three elements:
The level (owner level, group level, or other
level) to modify.
The permission (read, write, or execute) to modify.
The file files to modify.

Level Options

Table below lists the level options that can be used with the
chmod command.
Option Level Description
u Owner Owner of a file
g Group Group to which the user
belongs
0 Other All other users
a All Can replace u, g, or o

Linux File and Directory Permission Types

2009-06-29T01:57:00.000-07:00

File Permission Type

READ Enables users to open files and read its
contents using;more, cat, grep, sort, view.
WRITE Enables users to open a file and change its
contents using:vi, word, >
EXECUTE Enables users to execute files as commands

Directory Permission Type

READ Users can view filenames in the directory
WRITE Users can create, delete files in the directory.
EXECUTE Users can search in the directory and change
to it using the cd command.

MRTG Configuration for LINUX Redhat

2009-06-25T04:35:00.001-07:00

Configuring MRTG
The next step is to now configure MRTG for monitoring a network device. The below script can be run against
each server to create a cfg file for MRTG to use.
Create the user mrtg and the group mrtg then create the cfg directory to hold the configuration scripts and web
pages.
#mkdir /home/mrtg/cfg
#mkdir /home/mrtg/html
#!/bin/sh

PATH=$PATH:/usr/local/mrtg-2.9.14/bin; export PATH
cfgmaker --global “WorkDir: /home/mrtg/html/” \
--global “Options[ _ ]: growright, bits” \
--output “/home/mrtg/cfg/-mrtg.cfg public@.tornadogroup.com”
MRTG will create a cfg file for each server and place it into the /home/mrtg/cfg.
If the cfg file creatation fails, there can be two possible causes.
· Firewall is blocking connection
· Incompatible snmp on server
Testing cfg scripts
To test that statical information can be collected from a server, run mrtg with the cfg script.
#/usr/local/mrtg-2.9.14/bin/mrtg /home/mrtg/cfg/.cfg
Please note that the first couple of times errors regarding creating/moving are displayed this is normal and will
disappear. If they don’t then you have a configuration problem.
If the mrtg run successfully then an html file will be created displaying probably a blank chart until some stats
have been collected. Point a web browser at http:///mrtg/.html, if no html page
exists make sure that the cfg file points to the right location for the output.
Automating MRTG
Once all the cfg files have been created it’s best to automate the whole process via cron. Create a script like
below to call from cron and collect the stats.
/usr/local/mrtg-2.9.14/bin/mrtg /home/mrtg/cfg/.cfg
/usr/local/mrtg-2.9.14/bin/mrtg /home/mrtg/cfg/.cfg
/usr/local/mrtg-2.9.14/bin/mrtg /home/mrtg/cfg/.cfg
etc…………..
Now add to cron something like below:
5,10,15,20,25,30,35,40,45,50,55 /home/mrtg/cfg/

What you need for your summer vocation

2009-06-25T04:35:00.000-07:00

What you need for your summer vocation?
Before you can disembark on a summer vocation, you will need to pack your luggage. Depending on where you are planning to visit, the things you pack can be different. You must packing in advance and don’t forget important items if you are going for summer vocation on beach.
Many things you need for summer vocation some of listed below

1. Beachwear
2. Laptop
3. Camping Equipment
4. Apple Iphone for Entertainment

1. Very fist thing you need for beach beachwear costume. If you plan to get latest and safe the money get the beachwear products from savebucket.

2. To get connected with your business, friends and family make sure to pack your laptop if you need low price and slim laptop’s and also have huge collection of laptop’s available on savebucket. Savebucket is best place for the purchasing of summer vocation products.

3. Be sure do you have camping equipment very necessary for beach tour. In market many camping product available in market. But savebucket provide your camping equipment on low price

4. Apple i-phone is best for every one because this is slim and all feature avail able in apple products Apple recently introduce iPhone 3G the fastest, most powerful IPhone yet. iPhone 3GS features vide recording, Voice Control, up to 32GB of storage, and more. Apple i-phone and many more products available on savebucket shop.

The Fastest iPhone Ever
The first thing you’ll notice about iPhone 3GS is how quickly you can launch applications. Web pages render in a fraction of the time, and you can view email attachments faster. Improved performance and updated 3D graphics deliver an incredible gaming experience, too. In fact, everything you do on iPhone 3GS is up to 2x faster and more responsive than iPhone 3G.

Price Comparison
Every one want to save the money. As you know economic crisis every where. You have to compare the prices of all the products for your summer vocations I you want to compare the prices savebucket provide you for price comparison.

What Is iptables? Iptables will increase your network security

2009-06-24T00:58:00.000-07:00

Originally, the most popular firewall/NAT package running on Linux was ipchains, but it had a number of shortcomings. To rectify this, the Netfilter organization decided to create a new product called iptables, giving it such improvements as:

> Better integration with the Linux kernel with the capability of loading iptables-specific kernel modules designed for improved speed and reliability.

> Stateful packet inspection. This means that the firewall keeps track of each connection passing through it and in certain cases will view the contents of data flows in an attempt to anticipate the next action of certain protocols. This is an important feature in the support of active FTP and DNS, as well as many other network services.

> Filtering packets based on a MAC address and the values of the flags in the TCP header. This is helpful in preventing attacks using malformed packets and in restricting access from locally attached servers to other networks in spite of their IP addresses.

> System logging that provides the option of adjusting the level of detail of the reporting.

> Better network address translation.

> Support for transparent integration with such Web proxy programs as Squid.

> A rate limiting feature that helps iptables block some types of denial of service (DoS) attacks..
Considered a faster and more secure alternative to ipchains, iptables has become the default firewall package installed under RedHat and Fedora Linux

Detail Usage of Chmod why we use chmod command in linux

2009-06-23T11:52:00.001-07:00

'chmod' or "change mode" is the *NIX way of changing file permissions. It is VERY
different from DOS/Windows, if you are new to *NIX or always wondered what "drwxrxr-
x" meant read on.....
Where Windows/DOS machines realistically have one set of file permissions:
Read/Write - Archive - System - Hidden and then add on User Permissions to the
files and directories; *NIX breaks the permissions into three groups, 1 - user, 2
- group, 3 - world.
When you do an ls -la you might see the following:
[user@linux sites]$ ls -la
drwxr-xr-x 16 root root 1024 Oct 20 19:56 .
drwxr-xr-x 9 root root 1024 Sep 5 22:56 ..
drwxr-xr-x 9 foo user 1024 Sep 5 22:56 dir1
drwxr-xr-x 9 foo user 1024 Sep 5 22:56 dir2
drwxr-xr-x 9 foo user 1024 Sep 5 22:56 dir3
-rw-r--r-- 9 foo user 1024 Sep 5 22:56 file1
-rw-r--r-- 9 foo user 1024 Sep 5 22:56 file2
-rw-r--r-- 9 foo user 1024 Sep 5 22:56 file3
All the gobblygook at the beginning of each line is the file permissions. Note: To
*NIX, directories are just special files. In order to allow someone to 'traverse'
the directory tree, the user must have eXecute permissions on the directory even
if they have read/write privileges.
Within each set of permissions (you, group, world) there are three permissions you
can set: Read - Write - Execute. Therefore when you set the permissions on a file
you must take into account 'who' needs access.
Here's a stripped down list of the options chmod takes: (for more info do a man
chmod at the command line.)
chmod [-R] ###
-R is optional and when used with directories will traverse all the subdirectories
of the target directory changing ALL the permissions to ###. Very
useful but use with extreme caution.
The #'s can be:
0 = Nothing
1 = Execute
2 = Write
3 = Execute & Write (2 + 1)
4 = Read
5 = Execute & Read (4 + 1)
6 = Read & Write (4 + 2)
7 = Execute & Read & Write (4 + 2 + 1)
Of course you need a file name or target directory. Wild cards * and ? are
acceptable. If you don't supply the -R, with the target directory, the directory
itself will be changed, not anything within it.
Again you must supply the #'s in a set of three numbers (you, group, world).
To make a file readable and writable by you, and only read for your group, and no
access from the world,it would look like:
chmod 640 filename
The result would look like...
-rw-r----- 9 foo user 1024 Sep 5 22:56 file3
To make all files that end in .cgi read-write-executable for you, and readexecutable
for everyone else:
chmod 755 *.cgi
The result would look like...
-rwxr-xr-x 9 foo user 1024 Sep 5 22:56 file3.cgi
-rwxr-xr-x 9 foo user 1024 Sep 5 22:56 file4.cgi
Here are some standard permissions for files and directories:
[This is a gross approximation, a place to start. Your sysadmin maybe really loose
with permissions or a really tight-butt. Your mileage *will* vary.]
For Apache running as nobody:nobody.....Most Perl Scripts should be set to 755.
Most HTML files should be set to 644. And most data files that must be written to
by a web server should be 666. The standard directory permission should be 755.
Directories that must be written to by a web server should be 777.
If the web server is running within the same group as you....Most Perl Scripts
should be set to 750. Most HTML files should be set to 640. And most data files
that must be written to by a web server should be 660. The standard directory
permissions should be 750. Directories that must be written to by a web server
should be 770.
Your home directory should be 700. If you are operating a ~username type server,
the public_html directory should be 777. (You may also need to open up the home
directory to 755.)
Side Note: any file name that starts with a '.' is invisible to the webserver when
a directory list is generated. This is a quick and dirty way to hide a file.
Mutated into a life-size Dilbert doll, Anthony spends the days wedged into his
replica of Cardinal Fang's Comfy Chair coding solutions to the most thorny of
internet software problems.
4 comments on this article. Log in to add your comment Rate this article: Rate
this node 1 star.Rate this node 2 star.Rate this node 3 star.Rate this node 4
star.Rate this node 5 star.

How to Configure MySQL on Linux for Cacti

2009-06-22T12:14:00.000-07:00

Configure MySQL
Run these commands as root
cd /cacti-install
group-add cacti
useradd -g cacti cactiuser
/usr/local/mysql/bin/mysql
mysql> set password for root@localhost=password('rootpw');
mysql> create database cactidb;
mysql> grant all on cactidb.* to root;
mysql> grant all on cactidb.* to root@localhost;
mysql> grant all on cactidb.* to cactiuser;
mysql> grant all on cactidb.* to cactiuser@localhost;
mysql> set password for cactiuser@localhost=password('cactipw');
mysql> exit
MySQL Configure Script

How to Install PHP on Linux for Cacti

2009-06-22T12:13:00.000-07:00

Install PHP
Run these commands as root
cd /cacti-install
tar -zxvf php*
cd php*
./configure --prefix=/www/php --with-apxs2=/www/bin/apxs --with-config-filepath=/
www/php --enable-sockets --with-mysql=/usr/local/mysql --with-zlibdir=/
usr/include –with-gd
make
make install
cp php.ini-dist /www/php/php.ini
cp /www/conf/httpd.conf /www/conf/httpd.conf.backup
echo ####################### >> /www/conf/httpd.conf
echo # Added via Lee Carter's Script >> /www/conf/httpd.conf
echo ####################### >> /www/conf/httpd.conf
echo AddType application/x-tar .tgz >> /www/conf/httpd.conf
echo AddType application/x-httpd-php .php >> /www/conf/httpd.conf
echo AddType image/x-icon .ico >> /www/conf/httpd.conf
echo DirectoryIndex index.php index.html index.html.var >> /www/conf/httpd.conf
service httpd stop
service httpd start
PHP Install Script

How to Install Apache Server on Linux for Cacti

2009-06-22T12:12:00.000-07:00

Step by Step Installation
Install Apache
Run these commands as root
cd /cacti-install
tar -zxvf httpd*
cd httpd*
./configure --prefix=/www –enable-so
make
make install
cd /www/bin
cp apachectl /etc/init.d/httpd
y
cd /etc/rc3.d/
ln -s ../init.d/httpd S85httpd
ln -s ../init.d/httpd K85httpd
cd /etc/rc5.d/
ln -s ../init.d/httpd S85httpd
ln -s ../init.d/httpd K85httpd
/www/bin/apachectl start
Apache Install Script

How to Install MYSql on Linux for Cacti

2009-06-22T12:09:00.000-07:00

Install MySQL
Run these commands as root
cd /cacti-install
tar -zxvf mysql*
cd mysql*
./configure --prefix=/usr/local/mysql
make
make install
groupadd mysql
useradd -g mysql mysql
scripts/mysql_install_db
chown -R root /usr/local/mysql
chown -R mysql /usr/local/mysql/var
chgrp -R mysql /usr/local/mysql
rm -f /etc/my.cnf
cp support-files/my-medium.cnf /etc/my.cnf
echo /usr/local/mysql/lib/mysql >> /etc/ld.so.conf
echo /usr/local/lib >> /etc/ld.so.conf
ldconfig –v
cp support-files/mysql.server /etc/init.d/mysql
/usr/local/mysql/bin/mysqld_safe --user=mysql &
Echo
cd /etc/rc3.d/
ln -s ../init.d/mysql S85mysql
ln -s ../init.d/mysql K85mysql
cd /etc/rc5.d/
ln -s ../init.d/mysql S85mysql
ln -s ../init.d/mysql K85mysql
cd /etc/init.d/
chmod 755 mysql
MySQL Install Script

Computer Games and Young Generation

2009-06-18T02:01:00.001-07:00

Computer Games

California, Washington, Texas, New York and Massachusetts currently have the highest concentration of video game jobs. Collectively, these areas directly employ 16,604 workers and post 70 percent of the industry total indirect employment.

I found a really interesting game MMO online game: AION, I already mention many gaming server work online, AION have many features.
PowerWiki
Character Creating
Fortresses
Artifacts
Glossary
Legions

AION Hot Topics
Where’s Tutty?
Having a hard time finding Tutty? Find out where the elusive Porgus has gone.
Pathfinding
Think of pathfinding as an in-game GPS to make sure your don’t lose your way. It can be used to find location and NPCs.
Channels
You will discover the need for Channels when you first begin Aion. It can be an integral part to finding your friends and group members and playing in a relatively uncrowned setting.

AION also provide the forums support, if you feel any problem to play game or have any problem to understand it you can put the question in AION forums. In Featured media AION also provide, Wallpaper, Screenshot, Concept Art and AION Vides.
Very simple to play, just create a login and start playing game, for help read stories in AION forums. Different types of forum helps you online like, AION News & Announcements, Aion Character Image, Hot Videos General Discussion, Suggestion Box (your suggestions is important for AION) and technical Support.

Computer games, almost every 2nd Pearson like to play games on computer. This trend starts after 1990. As per survey 40% females and 60% males play games on computer. When any one get a free time, peoples like to spend time on computer. Some of peoples like to play games on web; many web sites provide this facility to play games on online. 10000 of gaming server every time online on web. Entertainment software is one of the fasters grosing industries in the U.S. Economy. In fact according to Pricewaterhouse Coopers, the sector remains “one of the above-average growth segments of the global entertainment industries through 2011.

Cacti SNMP Management

2009-06-18T02:01:00.000-07:00

Purpose
The purpose of this document is to explain how to install Red Hat’s Fedora Core 2 product and utilize a suite of applications for network based SNMP management. This document will take you thru step-bystep how-to install Linux on a new system and configure all the necessary tools that will get you a fully functional SNMP management station. SNMP management can be used to monitor just about anything on just about any IP enabled device.

Requirements
Before you get started make sure you have the following things:
· Fedora Core 2 CD’s 1 thru 3
· Active Connection to the Internet
· Computer that can be formatted and have a new OS installed from scratch
· About 3-4 hours of time

How it works
Cacti uses a suite of applications to do visual web front end graphing of results pulled via SNMP. These SNMP values can range from input/output rates on network / server interfaces to the number of macaddresses associated to a given access-point. Using SNMP to manage a network can provide a nontechnical central point of consolidation and health monitoring of your infrastructure. As stated earlier, SNMP is something that is already or can easily be enabled on many IP capable devices. Using SNMP to constantly pull statistical information and graphing that information can be useful in tracking things like disk utilization, network activity and much more. The CACTI application requires several utilities to be configured to work together in order to present the information in a GUI web front end. These utilities include a web server, a database, PHP and RDTOOL. All of which is freely available for the Linux operating system.

How to Install Install Moodle on Ubuntu

2009-06-17T12:21:00.000-07:00

On the command line, type:
cd /var/www
sudo wget http://download.moodle.org/stable19/moodle-latest-19.tgz
sudo tar -zxf moodle-latest-19.tgz
----
in ubuntu 8.04 it should be:
sudo tar zxf moodle-latest-19.tgz
----
sudo mkdir /var/moodledata
sudo chown -R www-data.www-data /var/moodledata

We now need to edit the location of the default web site. On lines five and ten, replace /var/www/ with /var/www/moodle/. Restart Apache.

sudo nano /etc/apache2/sites-available/default
sudo /etc/init.d/apache2 restart

Configure Moodle website
ifconfig (look for your server’s ip address on the 2nd line)
On another computer open a web browser and put in your server address
Complete the Moodle install using a secure username and password
Go to a bar for a few hours.
Come back and tell your boss that you FINALLY got the test server running.

Install Ubuntu With Easy Steps

2009-06-17T12:19:00.000-07:00

Start computer and use F12 to boot from CD.
Select Install to hard drive.
Select your language, country, and keyboard layout (i.e. English, United States, American English)
Select manually configure and set an IP address (or autoconfig if you don't know).
Enter your servername (i.e. moodletest)
Select to manually edit the partition table. I’m doing my testing on a standard 40GB harddrive and will modify these sizes for production.

Select to manually edit the partition table. I’m doing my testing on a standard 40GB harddrive and will modify these sizes for production.

/boot ext3 200MB bootable (may need to be under cylinder 1024 on your harddrive to be bootable )
/ ext3 10GB (files are relatively static)
swap 4GB (4xRAM if you don't have much memory, down to 1xRAM if you have gobs of memory)
/var ext3 26GB (variable content – uses rest of the drive)

Select your timezone. (i.e. Central)
Set clock to Universal Time.
Enter Administrators full name. (i.e. Joe Smith)
Enter account name. (i.e. joesmith)
Enter a secure password. (‘abcde’ is not a good one!)
Let the computer restart.
Log in your account.
Edit the /etc/apt/sources.list file. Remove the # mark on lines 22 and 38 to enable access to the universe package source and universe
security updates. You will need to re-enter your account password when sudo asks for it.