From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: rsync internal mirror configuration
Date: Tue, 12 Jul 2005 15:04:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20050712T160020-868@post.gmane.org> (raw)
In-Reply-To: 002901c586e2$ee3615e0$5f01010a@jnetlab.lcl
Dave Nebinger <dnebinger <at> joat.com> writes:
> > > and last run this daily on the server to keep it current?
> > > emerge -uDva world && repcacheman
> I forgot to mention that if your primary system is using the http replicator
> then it shouldn't be necessary to run repcacheman after each emerge.
> Repcacheman will a) ensure that packages retrieved via ftp are available
> from the cache and b) remove packages from the cache that are too old. This
> can easily be run as a monthly task if you primarily retrieve packages via
> http and not ftp.
Dave,
Your last 2 emails have given me much to think about. Give me some time to
finish the implementation, and digest all you have written.
I guess I have to run emerge sync and emerge -uD world on each client still,
but they use the http replicator instead of gentoo servers.... for both
updating the portage/rsync files and downloading the distfiles (via the http
replicator)?
That's OK, I like keeping it manual for now.
But I can rsync and 'emerge update' as many systems per day as I like now.
On the server, the emerge sync is automated via the /etc/crontab entry:
30 1 * * * root emerge sync 2<&1
I still have to run 'emerge -uD world' on the server/workstation
manually each day?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-12 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 13:09 [gentoo-user] Re: rsync internal mirror configuration Dave Nebinger
2005-07-12 15:04 ` James [this message]
2005-07-12 15:36 ` Dave Nebinger
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 18:18 [gentoo-user] " James
2005-07-11 18:37 ` Dave Nebinger
2005-07-12 2:42 ` [gentoo-user] " James
2005-07-12 6:51 ` A. Khattri
2005-07-12 15:16 ` James
2005-07-12 13:06 ` Dave Nebinger
2005-07-12 15:03 ` James
2005-07-12 15:29 ` Dave Nebinger
2005-07-12 16:03 ` James
2005-07-12 16:36 ` Dave Nebinger
2005-07-12 19:24 ` James
2005-07-12 19:47 ` Dave Nebinger
2005-07-13 14:35 ` James
2005-07-13 14:55 ` Dave Nebinger
2005-07-13 16:03 ` James
2005-07-13 14:51 ` James
2005-07-13 15:12 ` Dave Nebinger
2005-07-13 16:16 ` James
2005-07-13 17:54 ` A. Khattri
2005-07-13 20:35 ` James
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=loom.20050712T160020-868@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/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