From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: backup apparently not working
Date: Sat, 8 Nov 2008 10:11:32 +0900 [thread overview]
Message-ID: <97D2198646D94C718C59C8E0A60D8C58@bouncy> (raw)
In-Reply-To: <879ED343CB4F40F886B951480AB68CEF@tdsportable>
Exactly what I said.
Just because you execute a script from crontab does not mean it has all
environment variables set inside the script.
Your script is relying on the fact that the HOME environment variable is
set, which i'm sure it is when you run the script from the command-line,
however it might not be the case when the script is run from cron.
What user is running the crontab and what value do you expect HOME to be?
Also is the script running under /bin/bash and is the backquote expantion
actually working?
Modify your crontab so it echos your command into a temporary file so the
command that is executed is what you think it is.
Regards, Kerry.
----- Original Message -----
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, November 08, 2008 8:33 AM
Subject: Re: backup apparently not working
> what do you mean is it set in the crontab? I just execute that script from
> crontab. it's the script that's not working.
>
>
> Thanks,
> Tyler Littlefield
> email: tyler@tysdomain.com
> web: tysdomain-com
> Visit for quality software and web design.
> skype: st8amnd2005
>
> ----- Original Message -----
> From: "Kerry Hoath" <kerry@gotss.net>
> To: "Speakup is a screen review system for Linux."
> <speakup@braille.uwo.ca>
> Sent: Friday, November 07, 2008 4:32 PM
> Subject: Re: backup apparently not working
>
>
>> Is HOME set correctly in the crontab?
>>
>> Regards, Kerry.
>>
>> ----- Original Message -----
>> From: "Tyler Littlefield" <tyler@tysdomain.com>
>> To: "Speakup is a screen review system for Linux."
>> <speakup@braille.uwo.ca>
>> Sent: Saturday, November 08, 2008 7:52 AM
>> Subject: backup apparently not working
>>
>>
>>> Hello,
>>> First. I've partially figured out the problem.
>>> It's throwing a fit about removing leading slash.
>>> second, I've got the following line in a script:
>>> tar -czvf ~/backups/valiant/`date '+%m-%d-%Y_%H'`.tar.gz
>>> ~/valiant/moo/db.db
>>> when I ran that from the command line, it worked. when I tried to run it
>>> from a script, it "cowardly refused to create an empty archive," and
>>> then decided to try to run every file in my directory, it looks like.
>>> Ideas?
>>>
>>> Thanks,
>>> Tyler Littlefield
>>> email: tyler@tysdomain.com
>>> web: tysdomain-com
>>> Visit for quality software and web design.
>>> skype: st8amnd2005
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Kerry Hoath
` Tyler Littlefield
` Kerry Hoath [this message]
` Tyler Littlefield
` Tyler Littlefield
` Tyler Littlefield
` Chuck Hallenbeck
` luke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=97D2198646D94C718C59C8E0A60D8C58@bouncy \
--to=kerry@gotss.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).