procbatch - Process an INN funnel file or innfeed-dropped file
] [ -e peer
will take an INN funnel or innfeed-dropped
split it up by host for direct processing with innfeed
While funnel files will normally only be of interest after a crash,
may drop articles for a variety of reasons, not all of which
indicate a fundamental problem. For example, innfeed
may drop articles
when started and stopped in quick succession while INN processes a large
number of control messages (a temporary indisposition), or when INN feeds it
articles for a site that isn't in innfeed.conf
Every running innfeed
opens a file named
, which should normally always be zero length
and deleted on exit. If there are non-zero length files, innfeed
dropped some articles, and those dropped article files have to be processed or
those articles will never be sent to peers. Though news.daily
automatically process these files (invoking procbatch
), it is also
possible to do that manually. First make sure that the file doesn't correspond
to a currently running innfeed
, for example by calling "ctlinnd
An INN funnel file, or an innfeed-dropped
file, will usually be of the
pathname message-id peer1 peer2 peer3 ...
can alternatively be a storage API token.
will break this file up into files named peer1.tmp
, etc. of the format:
These tape files will be sorted and stripped of duplicate entries. Simply
renaming them to peer1
, etc. in a running
's backlog directory will cause them to be picked up
automatically by innfeed
(as set in in innfeed.conf
). Use the -m
flag to have
rename and move them into place automatically.
After running procbatch
, you may want to make sure that every generated
backlog file has a corresponding ".lock" file. Otherwise,
doesn't have that site configured as a peer, meaning your
may need fixing.
- Check for the existence of an article before writing
references to it to the tape files. Currently, this option can only be
used with a tradspool article store. Using it with any other spool format
will lead to all articles being dropped.
- -d outdir
- Put the output file(s) into the directory outdir
(defaults to pathtmp as set in inn.conf). When also
specifying -m, the temporary output files will still be put here
before being moved into their final location.
- -e peer
- Only process entries for peer.
- Display a short help screen.
- Directly append to tape files in innfeed's backlog
- Quiet mode: only display error messages.
- -s spooldir
- Use spooldir as the location of the article spool
(defaults to patharticles as set in inn.conf). This option
has an effect only on a tradspool storage system when also specifying
- -t backlogdir
- Use backlogdir as the location of the innfeed
backlog directory (the directory where the created tape files will be
put). Defaults to pathspool/innfeed. This option has an effect only
when also specifying -m.
- Unlink the input batchfile after processing.
- Add verbosity.
Take the file innfeed-dropped.B012345
, process its lines appending to
tapefiles in innfeed
's backlog directory, and remove it when done. Be
verbose while doing so:
procbatch -umv innfeed-dropped.B012345
Go through innfeed-dropped.B012345
saving entries for "peer1"
, but only if the articles are still available in the
procbatch -e peer1 -d /tmp -c innfeed-dropped.B012345
should be able to check for the existence of articles with any
kind of article store, possibly using grephistory
was written by James Brister and improved for speed by Clayton
This manual page was written by Florian Schlichting, with the help of a memo by
$Id: procbatch.pod 9371 2011-09-04 09:21:43Z iulius $