Hi Graham,
Thanks for your reply, and my humble apologies for the ridiculous length
of time in responding. I blame Christmas.
Have finally got back to this and I see the mistake in my script that
meant the output file wasn't even being created. Totally my fault.
Sorry.
Craig
On Sat,
On Fri, Nov 23, 2018 at 05:33:03PM -0800, Craig Hartnett wrote:
> Hi Graham,
>
> Thanks for your reply. Sorry for not getting back to you sooner.
No problem. I'm glad it worked out!
> The cron job has been happily running all week, so things are good.
> However, the script at
On Sun, Nov 11, 2018 at 06:02:31PM -0800, Craig Hartnett wrote:
> But I have to ask now, and it's something I think would be very useful
> to include on the "Getting started" page, how long should the first
> back-up take? I realise that's asking how long is a piece of string, but
> my first
Hi Graham,
On Thu, 2018-11-08 at 18:07 -0800, Graham Percival wrote:
> Welcome!
Thanks, and thanks for your reply.
> Careful there! "--exclude" only accepts a single value.
OK, that was clear in the config file, but not in the man page.
> "tarsnap -c -f foo" doesn't work, even if we
On Thu, Nov 08, 2018 at 07:57:42PM -0800, Michael Sierchio wrote:
>envoyé par un téléphone mobile avec «autocorrect» démoniaque
>On Thu, Nov 8, 2018, 18:07 Graham Percival <[1]gperc...@tarsnap.com
>wrote:
>
> Careful there! "--exclude" only accepts a single value.
>
>Except
On Thu, Nov 08, 2018 at 05:20:12PM -0800, Craig Hartnett wrote:
> Just signed up
Welcome!
> (e.g., tarsnap --dry-run --print-stats --humanize-numbers
> -c /media/USER/PATH
> --exclude /media/USER/PATH/.Trash-1000 /media/USER/PATH/lost
> +found /media/USER/PATH/OTHER-EXCLUDED-DIRECTORY)
Careful
