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

modflag: You can use the value in this field to further limit which groups are matched. The field should contain one of the following letters: M (moderated groups only), U (unmoderated groups only), A (all groups), X (removes the article). X results in every article that matches being deleted from every group that it is assigned to. keep: This field identifies how many days the article should be kept. The field should either contain a number or the word never. Articles are expired no sooner than the value set by keep. default: This field specifies the default value (in days). If an Expires: value is less than the default value, the default value is used. If the Expires: value is greater than the default, then the Expires: value is also honored. purge: This field identifies the outside boundary, in days, for how long articles should be kept. This boundary allows articles with Expires: headers to be accepted. If an article has an Expires: value that is longer than this purge value, the article is discarded at the time specified by purge. Tip Add your default newsgroups first. The expire rule that will be used is the last one that is matched. The contents of this file are less valuable for the cnfs storage method, because articles are cycled out when the buffer is full. The cnfs storage method therefore makes it difficult to control precisely when articles are purged. Allowing Users to Access Your Server As the INN software is delivered, your server will enable anyone with a login to your local host to access (or read) the news server. Requests from all other host computers are denied. To carry this out, the contents of the /etc/news/readers.conf file are set as follows: auth “localhost” { hosts: “localhost, 127.0.0.1, stdin” default: “” } access “localhost” { users: “” newsgroups: “*” access: RPA } In the above lines, the auth definition defines the localhost identity as including reader connections that come from different interfaces on the local computer. Access given to users from the localhost identity for all newsgroups consists of the ability to read articles (R), post articles (P), and post articles for moderated newsgroups (A). You can add access definitions to allow access to your INN server from other host computers. For example, if you wanted to add access to your INN server from all users from computers in the handsonhistory.com domain, you could use the following code: auth handson { hosts: “*.handsonhistory.com, handsonhistory.com” default: “” } access handson {
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.

Creating buffers for cnfs storage You can use the dd command to create a big file that exists on top of your regular file system. Here is an example of the dd command for creating a buffer file: dd if=/dev/zero of=/var/spool/news/articles/cycbuff bs=32k count=N In this example, N would be replaced with the size of the buffer that you want, divided by 32. The news user and newsgroup must be assigned ownership of the buffer file you create. The permission mode should be 0664 or 0660. For example: chown news /var/spool/news/articles/cycbuff chgrp news /var/spool/news/articles/cycbuff chmod 0664 /var/spool/news/articles/cycbuff Setting Up Expiration Times Expiration times for news articles are set in the /etc/news/expire.ctl file. Existing entries in that file can be used as your default expiration times. With the remember entry, an article (even if it is expired) is remembered for 10 days. In this way, if the article is offered from another news feed, you can accept it. Here is the remember entry included in expire.ctl: /remember/:10 If you want the Expires: headers to work, leave the following entry in your expire.ctl file: *:A:1:10:never Some groups are good to keep around forever. Here are two lines in the expire.ctl file that keep articles around longer for all newsgroups that end in .answers and all that begin with news.announce: *.answers:M:1:35:90 news.announce.*:M:1:35:90 Three different formats exist for entries in the expire.ctl file. The first format is represented by the /remember/ entry shown previously. The next is an entry for defining the expiration times associated with classes that are set in the storage.conf file. The other format contains five colon-separated fields that assign expiration to particular groups. Here are examples of the latter two formats: classnumber:keep:default:purge newsgroups:modflag:keep:default:purge The following are descriptions of each of the fields: classnumber: A number (0, 1, and so on) that corresponds with a class that is identified in the storage.conf file. newsgroups: The first field specifies which newsgroups are assigned to this expiration rule. As usual, you can use wildmat characters to match newsgroups. (Refer to the Understanding Wildmat Characters sidebar for details.)
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

} method cnfs { newsgroups: * class: 2 size: 0,3999 expires: 0s,4d options: SMALLAREA } method cnfs { newsgroups: * class: 3 size: 4000,1000000 options: BIGAREA } Notice that each of the cnfs storage methods in these examples applies to all newsgroups. Articles are stored in different buffers based on their class and size. The values in each of the options fields need to match entries in the cycbuff.conf file, as shown in the following section. Assigning buffers for cnfs storage Newsgroup articles are cycled out of your news server, for appropriate storage methods, based on the contents of the /etc/news/cycbuff.conf file. Here are some entries from the cycbuff.conf file that define the buffers used for the methods previously described: # The order of lines in this file is not important among the same item. # But all cycbuff items should be presented before any metacycbuff item. # 1. Cyclic buffers cycbuff:ONE:/export/cycbuffs/one:512000 cycbuff:TWO:/export/cycbuffs/two:512000 cycbuff:THREE:/export/cycbuffs/three:512000 # 2. Meta-cyclic buffers metacycbuff:BIGAREA:ONE,TWO metacycbuff:SMALLAREA:THREE In the cycbuff.conf file, all cyclic buffers (cycbuff) entries should appear before metacyclic buffers (metacycbuff). The second field of a cycbuff entry identifies the buffer’s name. In this example, the three buffer entries are named ONE, TWO, and THREE, respectively. (Each buffer name is later assigned to a metacyclic buffer.) The third field in each cycbuff field is the filename that identifies the path to the buffer file. The last field is the size of the buffer in kilobytes (1K equals 1024 bytes). In the metacycbuff entries, the second field contains the symbolic names of the metacyclic buffers (which are used in the options entries of the storage.conf file). The third field in each entry then assigns cycbuff entries to each metacyclic class. You can also add optional entries to this file, such as the following, to affect how buffering is done: cycbuffupdate: Reflects how many articles are stored between header updates. The default value is 25. refreshinterval: Reflects the number of seconds between the time a cycbuff header is read and the time it is reread. The default value is 30.
Note: If you are looking for cheap and reliable webhost to host and run your mysql application check mysql web server services.

expires: [,] options: } For each method name (timehash, cnfs, timecaf, tradspool, or trash), define the newsgroup(s) that applies to the method. Wildcard characters (*, ?, and so on) that can be used are described in the “Understanding Wildmat Characters” sidebar, earlier in this chapter. The optional class value can be assigned a number (0, 1, and so on) that matches an entry in the expire.ctl file where article expiration times are stored. The optional size value determines the minimum and maximum size an article can be. (A 0 as maxsize places no limits on article size.) The optional expires value determines the storage class based on the Expires: headers in the article. The options value (which is itself optional) can be used to set options that are specific to a method. Using the timehash storage method The timehash storage method stores newsgroup articles based on when your news server receives them. The following timehash method entry examples are contained in the storage.conf file itself. You can uncomment and modify these entries to create your own entries: method timehash { newsgroups: * class: 0 } method timehash { newsgroups: alt.binaries.* class: 1 size: 2,32000 } method timehash { newsgroups: alt.* class: 2 size: 1 } The first timehash entry matches all newsgroups that come in (*). The class number basically identifies a class that matches expiration time settings for newsgroups that are stored with the entry. (See the description of expire.ctl in “Setting Up Expiration Times,” later in the chapter, for information on how each class is defined.) The second timehash entry assigns a class (1) and size (2-byte to 32,000-byte limit) on newsgroups below the alt.binaries hierarchy. The third timehash entry is an example of assigning a class (2) and a size (1 to an unlimited number of characters) to all groups under the alt newsgroup hierarchy. Using the cnfs storage method The cnfs newsgroup storage method is an efficient way to rotate out newsgroup articles based on how many articles have been received (rather than just when they were received). Although this method is more complicated to configure, it is a good way to manage the size of your incoming news article database. Tip The INN installation instructions recommend the cnfs method of storing articles if you have a full news feed. This method is much more efficient than the timehash storage method for managing the volume of news that must be handled nowadays. Here are some examples of cnfs method entries from the storage.conf file. You can uncomment and modify these entries to suit your configuration: method cnfs { newsgroups: * class: 1 size: 0,3999 expires 4d1s options: FAQS
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

Unfortunately, the traditional way of storing news articles has become quite inefficient, given the huge volume of newsgroup articles these days. In addition to the traditional method, the INN news server offers the following other methods for storing newsgroup articles: timehash: Articles are stored in directories based on when they arrive. This method makes it easier to control how long articles are kept and prevents any directory from containing too many files. In the default news directory (/var/spool/news), the timehash method of storage creates directories based on the time articles are received. A timehash directory is in the form time-xx/bb/cc/yyy-aadd. Here, xx is a hexadecimal value of the storage class, and yyyy is a hexadecimal value of a sequence number. The other values represent the arrival time. cnfs: Articles are stored in buffer files that are configured before articles arrive. In this arrangement, when a new article arrives and the buffer is full, the new article replaces the oldest article. This is referred to as cyclical storage. When buffers are used instead of the file system, articles can be stored and served much faster. The downside to this method is that, because articles are overwritten automatically after the buffer limit is reached, it is harder to enforce a policy that retains articles for a set period of time. This method also requires more upfront configuration. timecaf: Lots of articles are stored in a single file with this storage method. This method can be about four times faster than the timehash method, though it gives you less control over the article spool. Because this method is relatively new, it has not been as well tested as other methods. Like timehash, the arrival time is used to name the files where articles are stored. tradspool: This is the original storage method for INN, where each article is stored as a separate file in a directory structure that is named after its newsgroup. While this method makes it easy to access articles on the news server, it has become ineffective for handling the volume of news that today’s news servers need to handle. trash: This method is only used for testing and for discarding articles based on your particular storage method. You cannot retrieve articles that have been assigned to the trash storage method. Activating different storage methods Storage methods used for your INN server are set in the /etc/news/storage.conf file. You can activate the timehash, cnfs, timecaf, tradspool, or trash storage methods by creating method entries in the storage.conf file. You can also assign different newsgroups and other attributes to different methods. (After this file is configured, no additional configuration file setup is needed for the timehash method; however, the cnfs method requires that you set up a cycbuff.conf file.) Note The storage.conf file replaces the now-obsolete storage.ctl file used for the same function in earlier releases. The format of a storage.conf file entry is as follows: method { class: newsgroup: size: [,]
In case you need affordable webhost to host your website, our recommendation is ecommerce web host services.

After the ME and innfeed! entries, you need to add entries that define the actual news servers to which you will feed articles. You should have one entry for each news server that you feed. The general format of those entries is as follows: remote-peer.domain.com/name-in-header.domain.com :newsgroup-list :Tm:innfeed! You need to replace remote-peer.domain.com with the FQDN of the server that you are feeding the news to. Next, replace the name-in-header with any alias names that the remote news server uses. The aliases are names that the remote news server puts in the Path header of the articles it forwards. (If no aliases exist, leave off the entire /name-in-header part.) You need to enter a newsgroup-list only if you want to feed newsgroups that are different from the newsgroups that are set by default (in your ME entry). The last part of the entry (:Tm:innfeed!) should be left as it is. If your server has the controlchan feature turned on (usecontrolchan: true in the inn.conf file), you should create an entry for the controlchan program in the newsfeeds file. This entry is meant to reduce the load if, in a short period of time, many control messages arrive at your news server. This entry runs the /usr/bin/controlchan command. controlchan! :!*,control,control.*,!control.cancel :Tc,Wnsm:/usr/bin/controlchan You can use a mind-numbing number of options within the newsfeeds file. If you are interested in delving deeper, read the comments in the newsfeeds file and refer to the newsfeeds manual page (type man newsfeeds). That manual page will also point you to related man pages. Getting a list of active newsgroups The Internet Software Consortium (http://www.isc.org/) maintains a listing of all officially active newsgroups. ISC stores these newsgroups in two different files: newsgroups and active. The newsgroups file contains each newsgroup name and a short description of the newsgroup. The active file stores the newsgroups to indicate which newsgroups your computer will offer. You can download the latest copies of the active and newsgroups files from the ISC FTP server: ftp://ftp.isc.org/pub/usenet/CONFIG/. From that directory, you can download either uncompressed versions of those files (each is more than 1MB in size) or compressed versions. Choose the active.gz and newsgroups.gz files, which you can uncompress in Red Hat Linux by using the gunzip command (gunzip active.gz newsgroup.gz). Place both the active and newsgroups files in your /etc/news directory. The newsgroups file provides the names and descriptions of the newsgroups offered to the users of your news server. The active file is the official list of newsgroups that is read by the innd daemon so that it knows what newsgroups it should accept articles for. You can edit the active file manually. Choosing How Articles Are Stored Traditionally, news servers have stored newsgroup articles in a very simple format. In the news spool directory (such as /var/spool/news), each article was stored under a subdirectory named after the newsgroup. For example, articles for the comp.os.linux.x newsgroup would be stored in the directory comp/os/linux/x in the news spool directory. Each article would be named by its unique message number and placed in that directory.
From our experience, we can recommend PHP5 Web Hosting services, if you need affordable webhost to host and run your web application.

*: An asterisk at the end of a newsgroup name indicates that all newsgroups following the one shown (those lower in the hierarchy) should be matched. [abc]: Any single character surrounded by the brackets is matched. For example, [abc]* matches any group name that begins with a, b, or c. You can also specify number or letter ranges, such as 3 9 or a r, with the braces to include all those numbers or letters. ?: A question mark matches any single character. So, c?mp matches comp, camp, and a lot of stuff that makes no sense at all. [^abc]: When a ^ is placed at the beginning of a set of brackets, the letters in the pattern match any character that is not in the brackets. For example, [^abc]* matches any group that does not begin with a, b, or c. The default /etc/news/newsfeeds file has only an ME parameter entry in it (and a lot of comments). The ME entry is required; you can have only one of them in your newsfeeds file, and it must appear before any other newsfeed lines. This entry contains a subscription list that is automatically added first to the subscription list of every other entry. Here is the default ME line: ME:!*/!local,!collabra-internal:: This default ME line specifically indicates some articles that are note forwarded. This line causes all incoming articles with local or collabra-internal in the Path header to be rejected. Articles that come in with either of those headers indicate that they are coming from a mis-configured server. Note The ME subscription entry defines only the subscription lists that you feed. It has nothing to do with the newsgroups that you receive. Newsgroups that you receive are defined in the active list. See the active(5) man page. The following is an example of an ME entry that includes additional restrictions: ME :*,@alt.binaries.warez.*,!junk,!control*,!local*,!foo.* /world,usa,na,gnu,bionet,pubnet,u3b,eunet,vmsnet,inet,ddn,k12 :: With this entry, all newsgroups are propagated to every server, with the exception of junk, control, local, and foo groups. The exclamation mark indicates that the name that follows is to be excluded. With the ME line set, you can go about defining how your specific newsfeeds are done. Here is an example of an innfeed line you can add to your newsfeeds file. This example funnels all newsfeeds to the startinfeed command. innfeed!: !* :Tc,Wnm*,S16384:/usr/bin/startinnfeed -y This line runs the startinnfeed command to start the innfeed program. The innfeed program, in turn, carries out the actual transfer of news articles between the news servers. Note If you have used an earlier version of INN, you should note that the overchan and crosspost programs are no longer used. The functions they used to perform are now incorporated into the INN server. With useoverchan set in the inn.conf, you can still use overchan. However, crosspost is no longer supported.
We recommend high quality webhost to host and run your jsp application: christian web host services.

connections from any one host to be five (unless overridden in a peer or group value). Two individual hosts are defined as news feeders: uunet (usenet1.uu.net) and vixie (gw.home.vix.com). The vixie definition is an example of using a key/value pair to override a default value. The group example is just a way to set key/value entries for several hosts at the same time. This example sets the maximum number of connections to 15 and assigns that value to all the peers in the group (data.ramona.vix.com and bb.home.vix.com). Then, as an illustration, that value is overridden for the second of those two hosts by setting the value to 20. The hostname can be a full host.domain name or an IP address. As you have already seen, max-connections can set the maximum number of connections that are enabled at a time from a host (0 enables unlimited connections). Here are some key/values that you can set globally, for a particular peer, or within a group: hostname: Identifies the host.domain name or IP address of the news server. streaming: Defines whether streaming commands are enabled (true or false). password: Assigns a string to this key that must be used by the host as a password before it can connect. By default, no password is required. noresendid: Causes the innd daemon to send a 431 RESENDID response to an article that has already been received from another peer. Configuring hosts that you feed The entries that you place in the /etc/news/newsfeeds file define how the articles that your news server receives are fed to other news servers. This file offers a lot of opportunity for configuration. The main reason this file is so complex is that it enables you to select which newsgroup articles to forward to each news server (based primarily on what they will accept). You can also set up definitions that apply to groups of servers. Note Despite its name, a news feed doesn’t actually feed news articles to another site. It simply reports that an article is available to be transferred to the other news server. Within the entries in the newsfeeds file, certain wildcard characters can be used to match or exclude whole sets of newsgroups. You can probably figure out how they work in the context of the examples. If not, however, you can refer to the Understanding Wildmat Characters sidebar for information on using the wildcard characters. Understanding Wildmat Characters When you need to identify newsgroups in your newsfeeds configuration file, you can use several different wildcard characters to simplify the process. These characters are defined on the wildmat man page (type man wildmat). Here is what they do: !: The exclamation point is used to indicate that the newsgroup name that follows should not be matched.
Please visit Domain Name Hosting services for high quality webhost to host and run your jsp applications.

pathoverview: /var/spool/news/overview pathrun: /var/run/news pathspool: /var/spool/news pathtmp: /var/lib/news/tmp Setting Up News Feeds For the flow of news articles to take place, news servers need to know about each other and need to be willing to exchange articles. The /etc/news/incoming.conf file lists the host computers that you allow to connect to feed your news. You use the /etc/news/newsfeeds file to set up where your news articles should be sent. You have to set up both of these files. Configuring hosts to feed you To configure the host computers that feed articles to your news server, you need to configure the /etc/news/incoming.conf file. In this file, you can set various key/value parameters that affect how these news feeds behave. Other entries are either peer entries or group entries. The key/value entries set values that are assigned to every peer and group entry. Those values can be overridden for particular peers or groups by adding new key/value entries within peer and group entries. Peer entries identify the FQDN of a computer that can feed news to your server, along with any key/value entries. Group entries are a way of assigning groups of peers to have particular key/value entries. The whole thing seems a bit complicated when all you are doing is defining which hosts can send news to you and how they are allowed to do that. Here is an example of the contents of an incoming.conf file from its man page: streaming: true # streaming allowed by default max-connections: 8 # per feed # A peer definition. peer uunet { hostname: usenet1.uu.net } peer vixie { hostname: gw.home.vix.com max-connections: 10 # override global value. } # A group of two peers who can open more # connections than normal group fast-sites { max-connections: 15 # Another peer. The “max-connections'’ value from the # “fast-sites'’ group scope is used. peer data.ramona.vix.com { hostname: data.ramona.vix.com } peer bb.home.vix.com { hostname: bb.home.vix.com max-connections: 20 # he can really cook. } } The only key/value pair in this example is max-connections: 8, which defines the maximum number of
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.

To have overview statistics related to the nnrpd daemon process logged to syslog, turn on the nnrpdoverstats parameters. By default, this parameter is off, as follows: nnrpdoverstats: false The nntpactsync parameter sets the number of articles that can come on an incoming channel before the activity is logged. The default value is 200 articles, as follows: nntpactsync: 200 The nntplinklog parameter indicates whether or not to place accepted articles’ storage API token. By default, this parameter is not on (false). nntplinklog: false To enable status monitoring, you need to turn on the status parameter by setting the value to a number. By default, this parameter is off (0). To have it turned on, set the value to the number of seconds between which status monitoring statistics are logged. You could set the value to 600 seconds as follows: status: 600 To enable performance monitoring, you need to turn on the timer parameter. By default, timer is off (0). To have it turned on, set the value to the number of seconds between which performance statistics are logged. You could set the value to 600 seconds as follows: timer: 600 System tuning parameters A set of low-level tuning parameters is available for tuning your INN server. In most cases, you shouldn’t need to change these parameters. These parameters include: badiocount, blockbackoff, chaninacttime, chanretrytime, icdsynccount, maxforks, nicekids, nicenewnews, nicennrpd, pauseretrytime, peertimeout, and rlimitnofile. If you are interested in learning more about the INN system tuning parameters, refer to the inn.conf man page. News directory parameters The inn.conf file sets the location of directories that contain newsgroup information. Although you shouldn’t have a need to change these locations, knowing where they are can be useful. The following text is taken from the inn.conf file, to show where the different news directories are located: # Paths patharchive: /var/spool/news/archive patharticles: /var/spool/news/articles pathbin: /usr/bin pathcontrol: /usr/bin/control pathdb: /var/lib/news pathetc: /etc/news pathfilter: /usr/bin/filter pathhttp: /var/log/news pathincoming: /var/spool/news/incoming pathlog: /var/log/news pathoutgoing: /var/spool/news/outgoing
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.