Re: amrecover as root on client NAK'd

2019-06-27 Thread Gene Heskett
On Thursday 27 June 2019 14:22:05 Debra S Baddorf wrote: > > On Jun 26, 2019, at 6:33 PM, Gene Heskett > > wrote: > > > > On Wednesday 26 June 2019 17:54:12 Nathan Stratton Treadway wrote: > >> On Tue, Jun 25, 2019 at 03:45:15 -0400, Gene Heskett wrote: > >>> I tried to run amrecover on picnc, bu

Re: ***UNCHECKED*** exact-match

2019-06-27 Thread Debra S Baddorf
> On Jun 27, 2019, at 7:38 AM, Nuno Dias wrote: > >> >> I guess another possible solution is to using disknames of a form >> that >> are designend to be unique, e.g. something like (not tested) >> >>> -- >>> MACHINE dir-main /dir { >>> tar >>> exclu

Re: amrecover as root on client NAK'd

2019-06-27 Thread Debra S Baddorf
> On Jun 26, 2019, at 6:33 PM, Gene Heskett wrote: > > On Wednesday 26 June 2019 17:54:12 Nathan Stratton Treadway wrote: > >> On Tue, Jun 25, 2019 at 03:45:15 -0400, Gene Heskett wrote: >>> I tried to run amrecover on picnc, but was NAK'd at every step. >>> This even though I have added the

Re: ***UNCHECKED*** exact-match

2019-06-27 Thread Nuno Dias
Hi Nathan, Thanks for the reply, in my configuration I need the includes, I make backups of terabytes of data, so split and the use of includes are essencial. I opened a bug in github. Cheers, Nuno On Wed, 2019-06-26 at 18:48 -0400, Nathan Stratton Treadway wrote: > On Wed, Jun 26, 2019 at