Re: Rerunning rejected replog fails (by design?)

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Friday, November 05, 2004 7:23 AM -0500 Frank Swasey 
<Frank.Swasey@uvm.edu> wrote:

> On Thu, 4 Nov 2004 at 11:53am, Quanah Gibson-Mount wrote:
>
> > As for the issue you saw, all you need to do is move the reject pieces
> > to a different directory, and then use slurpd in oneshot mode, rather
> > than doing the 6 steps you did...
>
> That may be true in 2.2, but back in 2.1 I had the same problem and
> solved it by replacing the timestamp in the rej files with the current
> time as output by `date +%s` on Linux.  That was AFTER I moved the
> reject files to the /tmp directory and ran slurpd from there -- it still
> went back to its "home" directory and read the slurpd.status file.

Wow, how odd... I've never had that problem in 2.2 or 2.1... Although I 
rarely get reject files, and generally they are because of timeouts, and 
the changes were valid anyhow. ;)

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html