newsrequeue(8) [debian man page]

NEWSREQUEUE(8)						      System Manager's Manual						    NEWSREQUEUE(8)

NAME

       newsrequeue - tool to rewrite batchfiles.

SYNOPSIS

       newsrequeue [ -a active ] [ -h history ] [ -d days ] [ -l ] [ -n newsfeeds ] [ input ]

DESCRIPTION

       Newsrequeue  can  be  used  to  rewrite	batchfiles after a system crash.  It operates in two modes.  In the first mode, it first reads the
       active (5) and newsfeeds(5) files to determine where the different newsgroups are to be distributed.  It then opens the	history  database.
       Once  the  files  are opened, newsrequeue reads from the specified input file, or standard input if no file is specified.  Each line should
       have a single Message-ID, surrounded in angle brackets; any other text on the line is ignored.  For example, the history file (or  trailing
       subset of it) is acceptable input to the program operating in this mode.

       Newsrequeue  uses  the  first two fields of the newsfeed entry -- the sitename and the excludes field, and the patterns and distribs field.
       It ignores all flags in the third field except for the ``N'' field, and also ignores the fourth field altogether.

       The output of newsrequeue consists of one line for each article that should be forwarded.  Each such  line  contains  the  Message-ID,  the
       filename, and the list of sites that should receive the article.  The output is suitable for piping into filechan(8).

       The second mode is used if the ``-l'' flag is given.  In this mode, it reads from the specified input file, or standard input if no file is
       specified.  Each line should look like an innd log entry.  It parses entries for accepted articles, looks up the Message-ID in the  history
       database to get the filename, and then scans the list of sites.

OPTIONS

       -a     To specify alternate locations for the active file, use the ``-a'' flag.

       -n     Use the ``-n'' flag to specify an alternate location for the newsfeeds(8) file.

       -h     Use the ``-h'' flag to specify a different location for the history database,

       -d     If the ``-d'' flag is used, then only articles that were received within the specified number of days will be processed.

       -l     Read innd type log entries instead of a history-file like entries.

HISTORY

       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  This is revision 1.2, dated 1996/10/29.

SEE ALSO

       active(5), ctlinnd(8), dbz(3), filechan(8), history(5), innd(8), newsfeeds(5), makeactive(8), makehistory(8).

																    NEWSREQUEUE(8)

HISTORY(5)							File Formats Manual							HISTORY(5)

NAME

       history - record of current and recently expired Usenet articles

DESCRIPTION

       The file /var/lib/news/history keeps a record of all articles currently stored in the news system, as well as those that have been received
       but since expired.  In a typical production environment, this file will be many megabytes.

       The file consists of text lines.  Each line corresponds to one article.	The file is normally kept sorted in the order  in  which  articles
       are  received,  although  this  is not a requirement.  Innd(8) appends a new line each time it files an article, and expire(8) builds a new
       version of the file by removing old articles and purging old entries.

       Each line consists of two or three fields separated by a tab, shown below as 	:
	      <Message-ID>   	   date
	      <Message-ID>   	   date	 	   files

       The Message-ID field is the value of the article's Message-ID header, including the angle brackets.

       The date field consists of three sub-fields separated by a tilde.  All sub-fields are the text representation  of  the  number  of  seconds
       since  the  epoch -- i.e., a time_t; see gettimeofday(2).  The first sub-field is the article's arrival date.  If copies of the article are
       still present then the second sub-field is either the value of the article's Expires header, or a hyphen if no expiration date  was  speci-
       fied.   If  an article has been expired then the second sub-field will be a hyphen.  The third sub-field is the value of the article's Date
       header, recording when the article was posted.

       The files field is a set of entries separated by one or more spaces.  Each entry consists of the name of the newsgroup, a  slash,  and  the
       article number.	This field is empty if the article has been expired.

       For  example, an article cross-posted to comp.sources.unix and comp.sources.d that was posted on February 10, 1991 (and received three min-
       utes later), with an expiration date of May 5, 1991, could have a history line (broken into two lines for display) like the following:
	      <312@litchi.foo.com>  		666162000~673329600~666162180  	
		  comp.sources.unix/1104 comp.sources.d/7056

       In addition to the text file, there is a dbz(3z) database associated with the file that uses the Message-ID field as a key to determine the
       offset  in  the	text  file  where the associated line begins.  For historical reasons, the key includes the trailing  byte (which is not
       stored in the text file).

HISTORY

       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  This is revision 1.12, dated 1996/09/06.

SEE ALSO

       dbz(3z), expire(8), innd(8), news-recovery(8).

																	HISTORY(5)