Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

uucpsend(8) [debian man page]

uucpsend(8)							Programmer's Manual						       uucpsend(8)

NAME
uucpsend - Alternative frontend for uucp batching SYNOPSYS
uucpsend [ -c config ] [ -f appendix ] sitename [ sitename ... ] This program offers a comfortable way to do news batching with the INN news system. Like the name assumes it is used for sites that are connected via UUCP. The idea behind the mechanism is taken from the nntpsend program which is already included in distributions of INN. The program does not do the batching itself. Instead it lets commonly used tools do the work. However it controls their behaviour. Using uucpsend you can define detailed how batching for each site shall take place in an easy fashion. In the file uucpsend.ctl(5) for each site your server feeds you can specify the size of batches, the maximal disk space that may be used by the uucp site, the header that should be written in the batch (e.g. funbatch, cunbatch, gunbatch etc.), the compression program to use as well as additional arguments passed to uux(8). The sitename should be the name of the site as specified in the newsfeeds(5) file. If no sitenames are passed to the program it will loop over all sites that described in the configuration file. This makes it easy to maintain sets of sites that are to be batched one after the other - contrary to batching through the whole day. A batcher(8) is launched for sites with queued news. Output is sent to the file /var/log/news/uucpsend.log. In order to keep from over- whelming the local system, uucpsend waits five seconds before the next site is fed. Uucpsend expects that the batchfile for a site is named /var/spool/news/out.going/sitename. To prevent batchfile corruption, shlock(1) is used to ``lock'' these files. It is useful to have cron(8) invoke uucpsend. When no sites are given on the command line, any flags given on the command completely describe how batcher operate. When no sites are given on the command line, then the information found in uucpsend.ctl becomes the default flags for that sites. OPTIONS
-f config Using this parameter you are able to specify a file different to PATH_UUCPCTL which defaults to /etc/news/uucpsend.ctl. -f appendix With the parameter ``-f'' you may specify another uucpsend.ctl(5) file. Information with regard to also given sitenames are read from the uucpsend.ctl-file. Please keep in mind that all default values are still read from the main uucpsend.ctl file. This fea- ture has been added to let big sites easily specify a different batching behaviour. HISTORY
Written by Martin Schulze <joey@infodrom.org>, derived mostly from nntpsend(8) by Landon Curt Noll <chongo@toad.com> and Rich $alz <rsalz@uunet.uu.net> for InterNetNews. SEE ALSO
innxmit(1), newsfeeds(5), uucpsend.ctl(5), nntppsend(8), nntppsend.ctl(5), shrinkfile(1). Infodrom 21 November 2001 uucpsend(8)

Check Out this Related Man Page

UUCPSEND.CTL(5) 						  Administration						   UUCPSEND.CTL(5)

NAME
uucpsend.ctl - list of sites to feed via uucpsend DESCRIPTION
The file /etc/news/uucpsend.ctl specifies the default list of sites to be fed by uucpsend(8). The program is able to read site information from other related configuration files as well. Comments begin with a hash mark (``#'') and continue through the end of the line. Blank lines and comments are ignored. All other lines should consist of six fields separated by a colon. Each line looks like site:max_size:queue_size:header:compressor:args The first field site is the name of the site as specified in the newsfeeds(5) file. This is also the name of the UUCP system connected to this site. The second field max_size describes the maximum size of all batches in kbytes that may be sent to this site. If this amount of batches is reached, this site will not be batched with this run and a reason will be logged into the logfile. This test includs all UUCP jobs, not only the ones sent to rnews (performing ``du -s''). The third field queue_size specifies the maximum size in kbytes of one batch. This argument is passed directly to batcher(8). The fourth field header defines the text that shall appear in the command header of every batch file. `#! ' is prefixed each batch. Nor- mally you'll need cunbatch for compress, gunbatch or zunbatch for gzip. This header is important since there is not standard way to handle gzip'ed batches. Using this and the next argument you're also able to use any compressor you like. So you receive a certain amount of flexibility by using uucpsend. If you don't want to have any compression leave the field empty. The fifth field compressor names a program that reads from stdin and writes to stdout. Normally it modifies the input stream by compress- ing it, such as compress(1) or gzip(1). The sixth field args consists of additional arguments that are passed directly to uux when sending the batch. One entry in the main configuration file is mandatory. There must exist a line containing the default values for all these variables. To achieve this the pseudo site /default/ is used. One default entry could look like this: /default/:2000:200:cunbatch:compress:-r -n This reflects a minimal setup. The maximal size that may be used by the UUCP spool directory is 2MB. Each batch will be max. 200 kBytes big. The header of each batch will contain the string `cunbatch' and compress(1) is used to compress the batches. `-r -n' is passed to uux(1) which means no notification will be sent if uux was successful and uux won't start the uucico(8) program when spooling the file. HISTORY
Written by Martin Schulze <joey@infodrom.org> for InterNetNews. Most of the work is derived from nncpsend.ctl(5) by Landon Curt Noll <chongo@toad.com> for InterNetNews. SEE ALSO
batcher(8), newsfeeds(5), uucpsend(8), uux(1). Infodrom 21 November 2001 UUCPSEND.CTL(5)
Man Page