innxmit articles from 2.2 machine => 2.3.2 machine

[Russ Allbery]

Steven L Sesar <ssesar at rcn.com> writes:

> Here, lemme try again and I'll post the relevant info from news.notice
> on both ends: On the receving end:

> Mar  1 20:20:06 newslocal innd: [ID 255605 news.warning] search1.mitre.org 
> connected 32 streaming allowed
> Mar  1 20:20:09 newslocal innd: [ID 903044 news.warning] search1.mitre.org:32 
> NCmode "mode stream" received
> Mar  1 20:20:09 newslocal innd: [ID 403891 news.warning] search1.mitre.org:32 
> closed seconds 3 accepted 0 refused 15 rejected 0 duplicate 0 accepted size 0 
> duplicate size 0

> On the transmitting end:

> Mar  1 20:20:10 searchsrv1 innxmit[14020]: newslocal stats offered 15 
> accepted 0 refused 15 rejected 0
> Mar  1 20:20:10 searchsrv1 innxmit[14020]: newslocal times user 0.010 system 
> 0.030 elapsed 2.805
> Mar  1 20:20:21 searchsrv1 innd: ME time 3614629 idle 3614584(33) artwrite 
> 0(0) artlink 0(0) hiswrite 0(0) hissync 0(9) sitesend 0(0) artctrl 0(0) 
> artcncl 0(0) hishave 0(0) hisgrep 0(0) perl 0(0)

The articles are already in the history file on the remote server.  You
have to get them back out of the history file before you can try again.
Unfortunately, it really sucks if something goes wrong on the first try
and you're feeding a running system, since the easy way (just erasing the
history file) will obviously hose a production system.

The entries will expire out of history after the /remember/ period in
expire.ctl.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>