From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: rsync internal mirror configuration
Date: Wed, 13 Jul 2005 20:35:51 +0000 (UTC) [thread overview]
Message-ID: <loom.20050713T221737-924@post.gmane.org> (raw)
In-Reply-To: Pine.BSO.4.58.0507131350040.32689@ida.bway.net
A. Khattri <ajai <at> bway.net> writes:
>
> On Wed, 13 Jul 2005, James wrote:
>
> > Ahhh that's it:
> > # cat /usr/portage/metadata/timestamp
> > Tue Jul 12 13:06:52 UTC 2005
> > # date
> > Wed Jul 13 12:05:26 UTC 2005
>
> On my machines, the master rsync server does a sync at 3am.
> The rest of the machines sync with the master server at 4am.
>
> This way there's no timing problems.
>
The timing problems have been eliminated. All dates and times
are within a few second of each other now.
System/OS clocks have all been sync to cell phone time.
Bios/Hardware clocks are now sync'd to the System/OS clocks.
> > The clock (hw and OS) were off, by about25 minutes but that has
> > been correct now. /etc/crontab was set for 1:30
> I run ntpd on ALL my machines (If you want to get fancy, you could setup
> your rsync server to also be a local NTP master server and have the other
> machines sync their clocks with this server too - makes even more sense
> if you use NFS).
I don't want to run NTP right now, but later I will.
I do not use NFS, as each system has plenty of disk space.
I'm not a big fan of NFS.... YMMV.
Thanks for the ideas, although these are not the source of
my problems. I'm implementing Dave's scripts tonight. Then
I'll see what happens....
I think the inherent entropy associated with patience, is my greatest
source of errors, presently... If I'm wrong, we'll adjust things
externally, and then continue the epic battle with entropy.
Thanks,
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-13 20:45 UTC|newest]
Thread overview: 23+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 13:09 Dave Nebinger
2005-07-12 15:04 ` James
2005-07-12 15:36 ` Dave Nebinger
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.20050713T221737-924@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