On Mon, 2002-04-01 at 01:03, Richard Ibbotson wrote:
> > #!/bin/sh
> > rsync -a /home/mydocs/ /home/richard/ > /dev/null 2>&1
> > mkdir -p /tmp/backup
> > export FILE=3Dbackup-`date +%Y%m%d`.tgz
^^^ FILE=backup...
> > tar -cz /home/richard > /tmp/mybackup/$FILE
> > mkisofs -r -J -o /tmp/backup.iso /tmp/backup
> > # cdrecord -v speed=3D2 dev=3D0,1,0 blank=3Dfast
^^^ ^^^ ^^^
speed=2 dev=0,1,0 blank=fast
> > cdrecord -v speed=3D2 dev=3D0,1,0 -data /tmp/backup.iso
^^^ ^^^
speed=3 dev=0,1,0
> > rm -rf /tmp/backup /tmp/backup.iso
>
>
> Okay ... I've done './backup' in /usr/bin to start the script. It
> worked fine until it got down to the bit about "cdrecord - v
> speed=3D2" and then it barfed.
Hmmm. Looks like an impedence mismatch between our mail clients, are you
using KMail at the moment? Any instance of '=3D' should be replaced with
'='. =3D is simply an encoding of =, but it should have been decoded at
your end...
'cdrecord -scanbus' will also tell you what dev= should be, it might not
be 0,1,0.
> Other thing is .. when I finally get the script to work the cron
> job.. ... you said use ... [at] daily. Thing is, I've always found with
> SuSE cron jobs that they are a bit choosy about the syntax that you
> use. In my own experience it doesn't like thing like [at] daily. It
> probably won't work. Anything else I can use ?
Check the man page. If it's a vixie cron, [at] daily will work.
Cheers,
Alex.
Attachment:
signature.asc
Description: This is a digitally signed message part