[gentoo-user] Re: Fetching updates with cron
* Michael Schreckenbauer (2003-08-07 16:37 +0200)
Am Donnerstag, 7. August 2003 16:15 schrieb Thorsten Kampe:
I have a vcron job[1] that syncs the portage tree und afterward
fetches available updates - at least that's how it is supposed to
work. The sync works fine and the fetch, too, at least according to
/var/log/emerge.log[2].
But actually the .tar.bz never reaches /usr/portage/distfiles, so I
have to execute emerge -fuD world manually. This happens with all
updates!
I even tried to search for the files - with locate - but they're not
on my harddisk.
Does anyone have a hint or idea?!
[1] 0 */12 * * * root /opt/gentoo-rsync/rsync-gentoo-portage.sh;
emerge -fuD world /dev/null [2] Started emerge on: Aug 07, 2003
12:14:020
Maybe I'm wrong, but isn't the '' at the wrong position? Afaik the line
should read:
0 */12 * * * root /opt/gentoo-rsync/rsync-gentoo-portage.sh;
emerge -fuD world /dev/null
Well (background) doesn't make much sense in a cron job in my
opinion.
I believe you are forcing your updates straight forward to /dev/null
Well no and yes:
man bash
There are two formats for redirecting standard output and standard
error: word and word. Of the two forms, the first is
preferred. This is semantically equivalent to word 21.
But the real culprit was *Prozilla*! I changed the $FETCHCOMMAND to
[1] and when I get back to the default wget - it works...!
Thorsten
[1] FETCHCOMMAND='/usr/bin/proz -r --no-netrc --no-getch --no-search -k=4
--timeout=300 -t=5 --retry-delay=15 --max-bps=0 ${URI} -P ${DISTDIR}'
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Fetching updates with cron
On Thursday 07 August 2003 11:57, Thorsten Kampe wrote: * Michael Schreckenbauer (2003-08-07 16:37 +0200) Am Donnerstag, 7. August 2003 16:15 schrieb Thorsten Kampe: I have a vcron job[1] that syncs the portage tree und afterward fetches available updates - at least that's how it is supposed to work. The sync works fine and the fetch, too, at least according to /var/log/emerge.log[2]. I use cron to sync portage and download updates too. But, I use a shell script to do everything and let cron combined with mail aliases send me the results. If you or anyone else is interested in the script I use, let me know and I will send it to you (or the list if it is allowed). -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Fetching updates with cron
2003 8 8 19:20Dhruba Bandopadhyay : If you or anyone else is interested in the script I use, let me know and I will send it to you (or the list if it is allowed). -- [EMAIL PROTECTED] mailing list Yes. Out of curiousity I would be interested in this script if you wouldn't mind :) AFAIK posting on list is okay but you can also send to my address if you like. List please... -- Robert B. Hawkins http://www.okihawk.org http://okiit.okihawk.org http://www.okiwell.org http://www.ospi.jp [EMAIL PROTECTED] Key fingerprint = 3B4D 6F6C A207 0CB7 4863 74F7 D63B D732 9764 6CC8 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Fetching updates with cron
Am Donnerstag, 7. August 2003 18:57 schrieb Thorsten Kampe:
* Michael Schreckenbauer (2003-08-07 16:37 +0200)
Am Donnerstag, 7. August 2003 16:15 schrieb Thorsten Kampe:
I have a vcron job[1] that syncs the portage tree und afterward
fetches available updates - at least that's how it is supposed to
work. The sync works fine and the fetch, too, at least according to
/var/log/emerge.log[2].
But actually the .tar.bz never reaches /usr/portage/distfiles, so I
have to execute emerge -fuD world manually. This happens with all
updates!
I even tried to search for the files - with locate - but they're not
on my harddisk.
Does anyone have a hint or idea?!
[1] 0 */12 * * * root /opt/gentoo-rsync/rsync-gentoo-portage.sh;
emerge -fuD world /dev/null [2] Started emerge on: Aug 07, 2003
12:14:020
Maybe I'm wrong, but isn't the '' at the wrong position? Afaik the line
should read:
0 */12 * * * root /opt/gentoo-rsync/rsync-gentoo-portage.sh;
emerge -fuD world /dev/null
Well (background) doesn't make much sense in a cron job in my
opinion.
Of course you are right here. I realized this, when I started to read your
answer.
I believe you are forcing your updates straight forward to /dev/null
Well no and yes:
man bash
There are two formats for redirecting standard output and standard
error: word and word. Of the two forms, the first is
preferred. This is semantically equivalent to word 21.
Ah, interesting. Thanks for this.
But the real culprit was *Prozilla*! I changed the $FETCHCOMMAND to
[1] and when I get back to the default wget - it works...!
Thorsten
[1] FETCHCOMMAND='/usr/bin/proz -r --no-netrc --no-getch --no-search -k=4
--timeout=300 -t=5 --retry-delay=15 --max-bps=0 ${URI} -P ${DISTDIR}'
Nice to hear everything works again :-)
HAND
Michael
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Fetching updates with cron
On 2003.08.07 12:57, Thorsten Kampe wrote:
[1] FETCHCOMMAND='/usr/bin/proz -r --no-netrc --no-getch --no-search
-k=4 --timeout=300 -t=5 --retry-delay=15 --max-bps=0 ${URI} -P
${DISTDIR}'
Did you try checking to see if ${DISTDIR} is a valid variable outside
of portage? Try a cron script that does something like:
echo ${DISTDIR} | mail -s distdir check myemailaddress;
or even
env | mail -s env myemailaddress;
I think that this was an invalid destination, so the download completed
and it saved them to nowhere. Try replacing it and manually entering
the /usr/portage/distfiles path.
--
Chris I
Actually, what I'd like is a little toy spaceship!!
pgp0.pgp
Description: PGP signature
