Web And Email Hosting, Jsp, Tomcat, J2Ee, Hibernate Programming Blog

you don’t need to set up the news user or create the spool directories. As INN is installed, you need only edit a few configuration files to get it going and turn on the service. (Though there isn’t much configuration needed at first, you will find yourself tuning it over time.) Note One thing you might need to do is run the makehistory command to create a history.hash file. This initializes the INN history database. Rich Salz created the INN software package. In recent years, its development was taken over by the Internet Software Consortium (at www.isc.org/products/INN). From ISC s home page, you can get other documentation and the latest software updates for INN. Starting with INN Because so much of the INN software package that comes with Red Hat Linux is already set up for you, it helps to find out first what you are starting with. Here is a quick rundown of how INN is set up for you after you install it from the Red Hat Linux distribution: News user: A news user is created in your /etc/passwd file. Ownership of news components (configuration files, spool files, and commands) is assigned to this user. The group name is also news. Its home directory is the news user’s spool directory (/var/spool/news). Configuration directory: Configuration files for INN are contained in the /etc/news directory. Sample files that you can use with INN are contained in /usr/share/doc/inn /samples. Spool directories: The INN spool directory structure, created in /var/spool/news, contains these directories: archive, articles, incoming, innfeed, outgoing, and overview. cron: Three entries exist for cron (two daily and one hourly). The two daily entries, in /etc/cron.daily, clean up the news service (remove old entries) and check that the news service is working once a day. The one hourly cron entry checks that the news service is running and then sends news articles to other NNTP sites. Mail command: The Mail Transfer Agent (MTA) used by news is set to the sendmail command in the inn.conf file. Reading access: As delivered, INN enables only users from the local host to read and post articles through your news server. Other hosts would have to be added to definitions in the INN server’s /etc/news/readers.conf file. Although a lot of the INN configuration is preset for you, some configuration is required before you can use the server. In particular, you must make some changes to the inn.conf (for general news server information), newsfeeds (to decide where your news articles are sent), and incoming.conf (where the articles you receive come from). If you use nontraditional storage methods (discussed later), some other files must also be configured. The inn.conf file is discussed in the next section, “Configuring the INN server.” Where your news articles are sent (newsfeeds) and where the articles you receive come from (incoming.conf) are discussed in “Setting Up News Feeds” later in the chapter. The information in these files is used by the innd daemon to manage incoming news feeds and by the nnrpd daemon to control which users can access the news server.
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

How long are articles stored? Articles that are stored using the traditional news storage method are held for 10 days by default. You can change that value (by resetting entries in the inn.conf and expire.ctl files). For the cnfs method, articles are rotated out automatically after the buffers are full. How to change the amount of time that news articles are stored is described in detail later in this chapter. How are servers to provide your news feeds located? You need to find one or more news servers to provide you with news feeds. Likewise, you need to configure your news server to feed other news servers with the articles that you want to pass on. You can ask your ISP whether it can provide you with a news feed or query a newsgroup that discusses how to set up news servers. How to set up news feeds is described later in the chapter. Tip Some news feed providers don’t want to be bothered with configuring partial news feeds. They will want you to take a full news feed or none at all. One way to use INN to configure a partial feed is by using the suck package. You can find the suck package using the rpmfind command or by visiting a Red Hat FTP mirror site. What are your newsgroup policies? Both the best and the worst of humanity seem to be unleashed in newsgroups. You need to set standards for your organization on what is acceptable usage of your newsgroups. For example, you may want to prevent the use of certain offensive newsgroups. Because the use of your news server reflects on your organization, you also want to teach your users good netiquette (Internet etiquette) when it comes to participating in newsgroups. Encourage your users to read articles from the news.announce.newusers newsgroup first. The articles in this newsgroup offer behavior guidelines when participating in newsgroups. Newsgroup primers are available that offer good advice, such as “Never forget that the person on the other side is human” and “Be careful what you say about others.” Guidelines for posting to newsgroups also exist. If users of your news server are abusive or antisocial, you as the administrator may find yourself the recipient of many complaints. Configuring an INN News Server The INN software lets you turn your Red Hat Linux system into a news server. INN is the most popular news server software for Red Hat Linux and other UNIX systems. All the daemon processes, commands, and configuration files that are needed to run a news server in INN come with your distribution of Red Hat Linux. The option to install news services is given to you during the Red Hat Linux installation process. If you did not install the news server software during the Linux installation, you can always install it later from the INN RPM file. You will first have to install the cleanfeed RPM, because the INN RPM depends on cleanfeed. Both RPM files are available on your Red Hat Linux media or from any Red Hat distribution mirror site. Obtain the files from the second Red Hat Linux installation CD (CD-2) and then, while logged in as root and within the directory containing the RPM files, type the following commands: # rpm -i cleanfeed-0.95.7b-12.noarch.rpm # rpm -i inn-2.3.2-5.i386.rpm It is possible that the version numbers of the RPM files you find will be different than those shown here. That is okay. Always use the latest version you can find. Red Hat Linux does a lot of the initial INN setup for you. You don’t need to build INN from source code, and
If you are looking for affordable and reliable webhost to host and run your business application visit our ftp web hosting services.

Planning Your News Server Setting up a news server can result in huge volumes of information traveling to and from your Red Hat Linux system. The task of setting up a news server to run smoothly can benefit greatly from a little bit of planning. Activities that go into planning a news server include: Determining whether you need a news server Choosing which newsgroups to offer from your server Choosing how articles are stored Locating one or more servers to provide your news feed Setting policies on acceptable usage of newsgroups Do you need a news server? This may sound strange, but the first thing you need to decide when planning a news server is whether or not you really need one. Unless you have a fairly large group of users who need to access newsgroups on a regular basis, you may simply want to have your people access newsgroups from a news server provided by your ISP. Maintaining a news server is resource-intensive. It involves a lot of network traffic, demands on the CPU, and disk space consumed. A full news feed can consume about 250GB of disk space per day. You can save a lot of space by not allowing groups that include binary files. Even then, however, you will still be consuming about 2GB of disk space per day. A news server can be contentious as well. Without firm policies, you can find yourself dealing with demands for newsgroups from your users that may not be appropriate for your organization’s goals. Which newsgroups should you offer? After you decide to set up a news server, choosing the newsgroups to offer will have an impact on all other aspects of setting up the server. Your decision will affect the amount of traffic coming into the server, the disk space used, and probably, above all, how your users can spend or waste their time with newsgroups. Basically, you will do this by restricting which newsgroups are accepted from the news feeds you define. For example, you may want to exclude many of the newsgroups in the alt.* hierarchy. How should articles be stored? The traditional method of storing news articles places each article in a separate file within the news server’s directory structure under the name of the newsgroup. This method is inefficient for large volumes of news. Therefore, INN offers several different methods of storing news articles. (See the section Choosing How Articles Are Stored, later in this chapter, for descriptions of each of these methods.)
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

Chapter 22: Setting Up a News Server Overview Newsgroups, the first popular offshoots of the early success of Internet e-mail, were started by people with common interests collectively maintaining e-mail lists to exchange messages on their subjects. As the lists became larger and harder to maintain, a new solution was needed. The result was Usenet newsgroups. Today, with literally thousands of newsgroups available (more than 36,000 newsgroups are listed officially with the Internet Software Consortium: isc.org), managing the servers that gather newsgroups and offering the newsgroups to people in an organization can be a daunting task. The difficulty of the task relates more to making decisions about what newsgroups to offer and how you want to manage news feeds with other servers than it does to implementing those decisions (although that is tricky, too). This chapter describes how to set up a news server on your Red Hat Linux system. It focuses on the most popular news server software InterNetworkNews (or INN configuration files). INN happens to be free and comes delivered with Red Hat Linux. Many other configuration files and methods of setting up a news server exist than those that are contained in this chapter. Use this chapter as a jumping-off point for configuring your news server. Then, refer to the man pages in /usr/share/man/*, the documents in /usr/share/doc/inn*, and the configuration files themselves for more information on setting up your news server. Caution Because a full INN news feed consumes massive amounts of disk space and network bandwidth, you need to configure it carefully. I strongly recommend getting help from experts as you tune your news server over time. You can get questions answered from the new.software.nntp newsgroup. There is also a database of INN information you can subscribe to from Mib Software called the Usenet RKT. To learn how to subscribe to the Usenet RKT, visit the following site: www.mibsoftware.com/0023.htm. Understanding News Transports In Red Hat Linux, the innd and the nnrpd daemons handle news transports. The innd daemon handles the incoming news feeds. When users request newsgroup articles, the innd daemon starts a nnrpd process to handle the request. The innd daemon is started from the innd script from one of the various system start-up directories. The innd daemon decides which incoming news articles to accept and which to reject, based on configuration information that is set up in a variety of configuration files. These include the active, newsfeeds, and incoming.conf files. (The INN configuration files for the INN news server are described later in this chapter.) The innd daemon also listens for user connections and manages the article spool directories. After a user requests an article, innd starts a nnrpd daemon to handle the request. It does that by checking the active and history fields to get information about the article. It then gets the article (taking it from the local spool directory) and forwards it to the user. Note The INN service is turned off by default. To turn it on, I recommend running the chkconfig command (as root user). Type chkconfig innd on to turn on the service. The next time your computer enters system state 3 or 5 (normal boot time), the INN service starts.
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.

Statistics Packages Available for Red Hat Linux Analyzing the transfer log by hand isn t much fun. Several packages have been written to automate this task, two of which are described below. Analog This free log file analyzer is very fast and easily configurable, and it produces very detailed output (including bar graphs and hypertext links). More information can be found at www.statslab.cam.ac.uk/~sret1/analog/. Wuage The output from this statistics program is detailed, graphical, and extremely configurable. A 30-day trial version is downloadable, but the full version can cost between $75 (for a single license) and $295 (for an ISP Multiple-Server license). Details are available at www.boutell.com/wusage/. Summary Web servers are responsible for storing and delivering the vast amount of content that is available on the World Wide Web to clients all over the world. Although several software packages are available for Red Hat Linux, the most popular (and the one that comes with Red Hat Linux) is the Apache Web server. This chapter describes how to install, configure, and run an Apache server in Red Hat Linux. The httpd daemon process handles requests for Web content (HTTP). Configuration files define what content is made available and how it can be accessed. In particular, the /etc/httpd/conf/httpd.conf file is used to configure the server. The apache package also includes facilities for logging error and transfer messages. You can look for the access_log and error_log files in the /etc/httpd/logs directory. The access_log file contains information on content requests that have been serviced by the server. The error_log file contains listings of error conditions that have occurred and times when service has been denied.
We would like to recommend you tested and proved virtual web hosting services, which you will surely find to be of great quality.

Analyzing Web server traffic The webalizer command can take Apache log files and produce usage reports for your server. Those reports are created in HTML format so you can display the information graphically. Information is produced in both table and graph form. To use the webalizer command, the webalizer package must be installed. You can run webalizer with no options and have it take the values in the /etc/webalizer.conf files to get the information it needs. As an alternative, you can use command-line options to override settings in the webalizer.conf file. To use the defaults, simply run the following: # webalizer If all goes well, the command should run for a few moments and exit silently. Based on the information in the /etc/webalizer.conf file, the /var/log/httpd/access_log log file is read and an index.html file is copied to the /var/www/html/usage/ directory. You can view the output by opening the file in any browser window. For example, you could type the following: # netscape /var/www/html/usage/index.html The output report shows a 12-month summary of Web server activity. On the bar chart, for each month a green bar represents the number of hits on the Web site, the dark blue bar shows the number of different files hit, and the light blue bar shows the number of pages opened. It also shows data for the number of visits and the number of sites that visited in the right column. The amount of data transferred, in kilobytes, is displayed as well. Figure 21-5 shows an example of a webalizer output file for a Web server that was launched in the past few days. Figure 21-5: Webalizer displays Web data in chart and column formats. Below the chart, a table shows daily and monthly summaries for activity during each month. Click the name of a month to see detailed activity. Tip Because webalizer supports both common log format (CLF) and combined log format, it can be used to display information for log files other than those produced for Apache. For example, you could display statistics for your FTP server or Squid server. Several other software tools are available for analyzing transfer statistics. The accompanying sidebar on statistics packages available for Red Hat Linux describes some of these packages.
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.

the filename in the Location directive, as in the lines below: and: Logging errors The error log contains messages generated by the server that describe various error conditions. Though the format of the error log cannot be customized, the ErrorLog and LogLevel directives in the httpd.conf file (as described in the section on configuring the server) can modify the filename and the amount of information that is logged. The default file is /etc/httpd/logs/error_log (which is a link to /var/log/httpd/error_log). A few sample lines from the error log are shown below: [Wed Nov 14 10:29:13 2001] [notice] Apache/1.3.12 (Unix) (Red Hat/Linux) configured — resuming normal operations [Wed Nov 14 10:43:07 2001] [error] [client 127.0.0.1] client denied by server configuration: /home/httpd/html/server-status [Sat Nov 14 10:06:42 2001] [error] [client 127.0.0.1] File does not exist: /home/httpd/html/newfile.html [Sat Nov 14 01:12:28 2001] [notice] caught SIGTERM, shutting down The first line indicates that the server has just been started and will be logged regardless of the LogLevel directive. The second line indicates an error that was logged to demonstrate a denied request (from Figure 21-4). The third line shows an error, which represents a request for a file that does not exist. The fourth line, also logged regardless of the LogLevel directive, indicates that the server is shutting down. The error log should be monitored periodically because it will also contain the error messages from CGI scripts that may need repair. Logging transfers Every incoming HTTP request generates an entry in the transfer log (by default, /etc/httpd/logs/access_log, which is a link to /var/log/httpd/access_log). Statistics packages and log file analysis programs typically use this file because manually reading through it can be a rather tedious exercise. The format of the transfer log can be altered by the LogFormat and CustomLog directives in the httpd.conf file (as described in the “Configuring the Server” section). If you attempted to access http://localhost/ following the installation procedure (from Figure 21-1), the following lines (in the “common” format) were written to the access_log: 127.0.0.1 - - [14/Nov/2001:23:32:28 -0400] “GET / HTTP/1.0″ 200 1945 127.0.0.1 - - [14/Nov/2001:23:32:36 -0400] “GET /poweredby.gif HTTP/1.0″ 200 1817 127.0.0.1 - - [14/Nov/2001:23:32:36 -0400] “GET /icons/apache_pb.gif HTTP/1.0″ 200 2326 Viewing the server-info and server-status pages (as shown in Figures 21-2 and 21-3, respectively) generated the following entries: 127.0.0.1 - - [14/Nov/2001:23:40:41 -0400] “GET /server-info HTTP/1.0″ 200 42632 127.0.0.1 - - [14/Nov/2001:23:41:49 -0400] “GET /server-status HTTP/1.0″ 200 1504 The denied attempt to access the server-status page (from Figure 21-4) logged the following line (note the 403 server response code): 127.0.0.1 - - [11/Apr/2001:23:43:07 -0400] “GET /server-status HTTP/1.0″ 403 211
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.

Displaying server status The contents of the server-status page include version information for the server, the current time, a timestamp of when the server was last started, and the server s uptime. The page also details the status of each server process, choosing from several possible states (waiting for a connection, just starting up, reading a request, sending a reply, waiting to read a request before reaching the number of seconds defined in the KeepAliveTimeout, performing a DNS lookup, logging a transaction, or gracefully exiting). The bottom of the server-status page lists each server by process ID (PID) and indicates its state, using the same possible values. Figure 21-3 is an example of this page. Figure 21-3: The Apache server-status page displays general Apache information and reports on individual server process activities. The server-status page can also perform automatic updates to provide even closer monitoring of the server. If the URL http://localhost/server-status?refresh=40 is specified, the server-status page displayed in your browser will be updated every 40 seconds. This enables a browser window to be devoted entirely to continually monitoring the activities of the Web server. Further security of server-info and server-status Because both the server-info and server-status pages contain private information that should not be accessible to just anyone on the network, there are a few extra ways you can secure that information. You can restrict that information only to the local host; however, in some environments that may not be practical. If you must allow other machines or networks access to such detailed configuration information, allow only as many machines as is necessary, and preferably only those machines on your local network. Also, be aware that, in the wrong hands, the information displayed by the server-info and server-status pages can make it much easier for the security of your entire machine to be compromised. Figure 21-4 shows the error message that should be presented to hosts that do not have access to the server-status page. Figure 21-4: Deny server-status and server-info access to hosts on external networks, and perhaps to any machine other than the server. It may also be beneficial to change the URL used to reference both of the aforementioned pages. This is an example of security through obscurity, which should not be relied on but which can make it just a little more difficult for unauthorized individuals to obtain information about your Web server s configuration (particularly if you cannot restrict such connections to the local network). To accomplish this, simply change
Check Tomcat Web Hosting services for best quality webspace to host your web application.

-D TYPES_CONFIG_FILE=”/etc/httpd/conf/mime.types” -D SERVER_CONFIG_FILE=”/etc/httpd/conf/httpd.conf” -D ACCESS_CONFIG_FILE=”/etc/httpd/conf/access.conf” -D RESOURCE_CONFIG_FILE=”/etc/httpd/conf/srm.conf” -X Only the single master daemon process is started, and no other httpd processes will be spawned. This should be used only for testing purposes. Monitoring Server Activities Apache provides two unique built-in methods to check the performance of your Web server. The server-info handler can be configured to display a detailed summary of the Web server s configuration. The server-status handler can be configured to show information about server processes. You can activate these services by adding the following lines to the /etc/httpd/conf/httpd.conf file, respectively: SetHandler server-info order deny,allow deny from all allow from handsonhistory.com SetHandler server-status order deny,allow deny from all allow from handsonhistory.com In this example, all computers in the handsonhistory.com domain can display the server-info and server-status pages. You can change handsonhistory.com to any domain or host that you choose. Displaying server information The Server Information (server-info) page contains the server version information and various general configuration parameters and breaks up the rest of the data by module. Each loaded module is listed, with information about all directives supported by that module, and the current value of any defined directives from that module. The Server Information is usually quite verbose and contains much more information than can be displayed in Figure 21-2, which shows only the links to each module s section and the general Server Settings section. Figure 21-2: The server-info page displays server and module information.
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.

Read the configuration files and then process the directive. This may supersede a definition for the directive within the configuration files. -C directive Process the directive and then read the configuration files. The directive may alter the evaluation of the configuration file, but it may also be superseded by another definition within the configuration file. -d directory Use directory as the ServerRoot directive, specifying where the module, configuration, and log file directories are located. -D parameter Define parameter to be used for conditional evaluation within the IfDefine directive. -f file Use file as the ServerConfigFile directive, rather than the default of /etc/httpd/conf/httpd.conf. -h Display a list of possible command-line arguments. -l List the modules linked into the executable at compile-time: Compiled-in modules: http_core.c mod_so.c -L Print a verbose list of directives that can be used in the configuration files, along with a short description and the module that contains each directive. -S List the configured settings for virtual hosts. -t Perform a syntax check on the configuration files. The results will either be: Syntax OK or (for example): Syntax error on line 118 of /etc/httpd/conf/httpd.conf: ServerType must be either ‘inetd’ or ’standalone’ -T Same as -t, except that there is no check of the DocumentRoot value. -v Print the version information: Server version: Apache/1.3.12 (Unix)(Red Hat/Linux) Server built: Aug 7 2000 06:20:48 -V List the version information and any values defined during compilation: Server version: Apache/1.3.12 (Unix)(Red Hat/Linux) Server built: Apr 7 2000 06:20:48 Server’s Module Magic Number: 19990320:7 Server compiled with…. -D EAPI -D HAVE_MMAP -D HAVE_SHMGET -D USE_SHMGET_SCOREBOARD -D USE_MMAP_FILES -D USE_FCNTL_SERIALIZED_ACCEPT -D HTTPD_ROOT=”/usr” -D SUEXEC_BIN=”/usr/sbin/suexec” -D DEFAULT_PIDLOG=”/var/httpd/httpd.pid” -D DEFAULT_SCOREBOARD=”/var/httpd/httpd.scoreboard” -D DEFAULT_LOCKFILE=”/var/httpd/httpd.lock” -D DEFAULT_XFERLOG=”/var/log/httpd/access_log” -D DEFAULT_ERRORLOG=”/var/log/httpd/error_log”
In case you need quality webspace to host and run your web applications, try our personal web hosting services.