From: Justin C on
On 2010-07-07, Big and Blue <No_4(a)dsl.pipex.com> wrote:
> On 07/07/10 16:36, Justin C wrote:
>>
>>
>> Ah! OK. I will give that a try. cron will run it over-night and I'll see
>> how it got on tomorrow morning.
>
> A strange (to me) debugging tactic.
>
> Why not create a much cut-down version that covers an example of what you
> wish to do and run that now? In a few minutes. So that when the cron job
> runs overnight you can have a high expectation that now it *will* do what
> you require.

Because it's backing up more than I want and the device has the
capacity. If I make the change, and all is good, then there's no more to
do, it's done. If it throws up an error, well, I'll fix it tomorrow
(today now). Also I've got my head stuck in a 500 line Perl programme
that has to play nice with a bash script and I can't focus on both!

Justin.

--
Justin C, by the sea.
From: Justin C on
On 2010-07-07, Paul Martin <pm(a)nowster.org.uk> wrote:
> In article <slrni397on.8c1.justin.1007(a)zem.masonsmusic.co.uk>,
> Justin C wrote:
>
>> Looking again at what I'm backing up, I might do a "cd /home" first and
>> then backup "*" rather than "cd /" and backing up "home", I can then
>> change the paths in the exclude file to */justin/tmp_img_dir/* or
>> similar. I think that is more tidy.
>
> tar -c -C /home -f $tape --exclude-from /var/local/backup_excludes .
>
> Then have the patterns be
>
> ./justin/tmp/tmp_img_dir
> ./justin/.mozilla/Cache
> ./ali/Cookies

I'm afraid that isn't it. Or at least, it didn't work here. The correct
answer for the patterns in the exclude file is:

justin/tmp/tmp_img_dir
justin/.mozilla/Cache
ali/Cookies

Thank you for your suggestion, and others for theirs.

Justin.

--
Justin C, by the sea.