public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 16:03:58 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050712T174726-422@post.gmane.org> (raw)
In-Reply-To: 005e01c586f6$7997de80$5f01010a@jnetlab.lcl

Dave Nebinger <dnebinger <at> joat.com> writes:


> > OK but can't I do that with a simple mode to the /etc/crontab ?:
> > 30 1 * * * root emerge sync 2>&1

> Yes, but I do a little more in my script and want the pieces to be
> synchronized.  As you saw in the script not only do I emerge sync but I also
> update the eix and esearch databases (both are cached package search/query
> tools that kick the crap out of "emerge --search").

I'm going to test your scripts and look at this for a while....

> I've been considering adding an "emerge --fetchonly" line to the script but
> don't yet have the warm and fuzzies about the http-replicator script.

Yes, well I'm going to go slowly with this
until I have the warm feeling and some
happy experience over time.
I'd be interested in keeping up with your scipt enhancements.
If it's not too much trouble, when you are happy with
some enhancements, send them to me for testing....

> > This script is for the internal rsync/replicator server?

> Runs on all of them.  All of them need to sync and I like being able to
> query from whatever system I'm on.

Yea, I was not sure, but it makes
sense.

> > OK, the port has changed. What's the deal about that?

> Most local http daemons run on 8080 or 8088; I just didn't want to deal with
> conflicts so I chose my own number.

Yea, I might change the port number...if I see problems. 

> > OK thanks for the script. I'll have to study it, test it and let you know
> > how it goes...

> They've been working out great for me.  I've recently added a
> 'revdep-rebuild' script so I can be reported of packages in need of fixing
> (in case I miss the step manually).

Can you send me a copy of that script or post it to this thread?


> In your case I'd probably ensure the kids logins are typical user logins (no
> update capability).  Run the scripts (or similar scripts) to automate the
> syncing and reporting.  Keep ssh running on their systems.  Hold off on
> updates until they run into something that breaks or until a critical
> package update is released.  Then you can ssh in and emerge stuff until it
> works.

I'll take this under consideration. My purpose in extending automated
updates, is to be able to manage a large number of embedded gentoo 
devices in the future.  Roll-back and Recovery mechanism will be 
added later. Besides Gentoo needs to leave the laboratory
(purvey of experts) and enter the world of normal humanoids. That will
force the Gentoo community to make Gentoo a commodity technology for
the world's normal folks.....gentoo's destiny in my opinion.

Using kids as experiments and developing baseline analysis semantics, is
of great fun... (Hell, that's what God gave them to us for: to 
experiment with them and then explain where dad messed up and dad's
newest ideas.) Even their friends like the approach of experimental
parenting... Furthermore, as an engineer, I often tell my clients 
that something works with the children or that children understand the
new technology, so maybe management can adapt too...)

YMMV

James

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-12 16:10 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 [this message]
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
  -- 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.20050712T174726-422@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