public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Cc: <news@sea.gmane.org>
Subject: RE: [gentoo-user]  rsync internal mirror configuration
Date: Mon, 11 Jul 2005 14:37:16 -0400	[thread overview]
Message-ID: <001501c58647$908432b0$5f01010a@jnetlab.lcl> (raw)
In-Reply-To: <loom.20050711T201402-372@post.gmane.org>

> I did not see what determines what (during a 24 hour
> period) controls the time the internal rsync mirror
> goes out to  update the files? Obviously I only
> want the rsync internal server to update once a day.

Following that document means that you are exporting the /usr/portage
directory on the local box for your internal servers.

This has some implications:

1. the /usr/portage directory is not updated by this process.  You still
need to emerge --sync the local system.  This is QED by a cron task.

2. This only syncs up the /usr/portage tree but does not help reduce the
number of distfiles downloads.  Look at http://gentoo-wiki.com/Http_proxy
and http://gentoo-wiki.com/HOWTO_Download_Cache_for_LAN-Http-Replicator for
instructions there.  By using the http-replicator you only will be
downloading distfiles/patch files once.

3. There is no additional disk space requirements for the rsync mirror;
you're serving up your existing /usr/portage directory so it's not like you
wouldn't have those files around anyway.



-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-11 18:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 18:18 [gentoo-user] rsync internal mirror configuration James
2005-07-11 18:37 ` Dave Nebinger [this message]
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='001501c58647$908432b0$5f01010a@jnetlab.lcl' \
    --to=dnebinger@joat.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=news@sea.gmane.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