Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

snfetch(8) [debian man page]

snfetch,v0.3.8(8)					      System Manager's Manual						 snfetch,v0.3.8(8)

snfetch - fetch articles. SYNOPSIS
snfetch [-r] [-t timeout] [-c depth] group [serial [max]] DESCRIPTION
snfetch expects to read NNTP from file descriptor 6, and write NNTP to file descriptor 7, which descriptors must have already been open. Articles retrieved are written to descriptor 1. Each article displayed is separated from the next by a dot on a line by itself. These articles are NNTP safe, in the sense that double-dot unquoting is not done, and all lines end in CR-LF. snfetch expects to begin it's NNTP speech by giving the GROUP command. The upstream server's greeting must have already been read some other way. Likewise, when snfetch is done, it will not send a QUIT command. The output is suitable for feeding to snstore. snfetch always checks the article ID of the prospective article before retrieving it. If the ID already exists in the ID database, the article will not be retrieved. Note that this does not guarantee that all articles retrieved will be unique. snfetch does not guarantee to leave the NNTP conversation in a decent state (there might be more data to read, but snfetch aborted part way). You will need to be root or own /var/spool/sn in order to run this program. It is not safe to direct the output of several snfetches to the same pipe descriptor, but a file descriptor is all right. OPTIONS
-t timeout snfetch will wait only timeout seconds (default 180) for data before giving up, if the server doesn't respond. -r Output in news batch format instead. All articles will take the #! rnews form only, even if there is just one article, all lines end in bare linefeed, and dot-unquoting is performed. -c depth Employ a command pipeline of depth depth. NNTP command pipelining is not officially sanctioned, so by default no pipeline is used. However, a pipeline with a depth greater than 0 will substantally reduce transaction latency if the server accepts it. A respectable value for depth might be between 1 and 5. ARGUMENTS
snfetch takes the name of a single newsgroup on its command line. If serial is given, this is taken to be the first article number on group on the server to fetch. If max is specified, this is taken to be the maximum number of articles to fetch. The first article retrieved may be after serial if max would be violated. If max is not specified, there is no limit. ENVIRONMENT VARIABLES
SNROOT If this is set and is not empty, the value is used in place of /var/spool/sn, the default news spool directory. FILES
/var/spool/sn/newsgroup/.serial If serial is not specified, the starting serial number is taken from the file /var/spool/sn/newsgroup/.serial. This defaults to 0 if the file can't be read. /var/spool/sn/newsgroup/.serial.tmp If snfetch exits with success (0), the new serial is written into this file. The original file /var/spool/sn/newsgroup/.serial is readonly by snfetch. /var/spool/sn/newsgroup/.max If max is not specified on the command line, max is read from this file. If the file cannot be read or does not exist, there is no limit. EXIT CODES
snfetch exits 1 on usage error, 2 on system failure, 3 on protocol error, 4 on read timeout, and 0 on success. SEE ALSO
snstore (8), snget (8) N.B. Harold Tay snfetch,v0.3.8(8)

Check Out this Related Man Page

snprimedb,v0.3.8(8)					      System Manager's Manual					       snprimedb,v0.3.8(8)

snprimedb - feed the sn database. SYNOPSIS
snprimedb [-i] (no arguments) DESCRIPTION
snprimedb reads records from its standard input and enters them into the database. The database is appended to; if you want to start a new database, you would delete the database files .chain, .table, .newsgroup before running this program. The main purpose of snprimedb is to rebuild the ID database. Then its input is usually obtained from snscan. If the option -i is given, simply initialize the database files if they do not exist, and exit. Input lines are of the format newsgroup id serial where newsgroup is the newsgroup the article may be found in, id is its message id, and serial is the local serial num- ber of that article in that newsgroup. If newsgroup is the special name =junk, then the whole line is ignored. You will need to be root or the owner of /var/spool/sn to do this. BUGS
snprimedb does not check to see that the articles really exist. Also the size of the hash table is fixed at compile time. Under degenerate conditions, the hash table file .chain (see below) could grow very large, with reclaimed space remaining unused. This is due to the very simple file space allocator, which doesn't know how to coalesce adjacent free areas. It doesn't know how to split them either. The allocator assumes that the shape of the distribution of record lengths remains quite constant over time. The hash table database doesn't make any attempt to reduce its footprint. This should be acceptable, since the database is shared. ENVIRONMENT VARIABLES
SNROOT If this is set and is not empty, the value is used in place of /var/spool/sn, the default news spool directory. FILES
/var/spool/sn/.table snprimedb uses this file as the index of the hash table, and ... /var/spool/sn/.chain as the hash chains, and ... /var/spool/sn/.newsgroup to attach an integer identifier to each newsgroup name. This file is a human-readable flat text file. N.B. Harold Tay snprimedb,v0.3.8(8)
Man Page

Featured Tech Videos