From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] User eix-sync permissions problem
Date: Tue, 11 Feb 2014 11:12:41 +0000 [thread overview]
Message-ID: <20140211111241.6b5caf11@digimed.co.uk> (raw)
In-Reply-To: <20140211110710.GA21214@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On Tue, 11 Feb 2014 06:07:10 -0500, Walter Dnes wrote:
> > emerge --sync X number of times daily in a cron
> >
> > emerge -avuND world deliberately and manually as the sysadmin at your
> > leisure.
> >
> > Two different actions in time.
>
> Assume you sync once a day, and update once a week, the first 6 syncs
> would be mostly wasted.
They wouldn't because eix-sync would inform you of any updates that you
may not ant to wait for. More importantly, if your cron script also runs
glsa-check, you would know about any potential vulnerabilities on your
machine the day they are announced rather than leaving yourself wide open
for up to a week.
--
Neil Bothwick
If man ruled the world:
Daisy Duke shorts would never go out of fashion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-11 11:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 16:05 [gentoo-user] User eix-sync permissions problem Stroller
2014-02-10 16:55 ` Gleb Klochkov
2014-02-10 17:09 ` Stroller
2014-02-10 19:03 ` Walter Dnes
2014-02-10 19:29 ` Alan McKinnon
2014-02-10 23:10 ` Kerin Millar
2014-02-10 23:57 ` Walter Dnes
2014-02-11 0:05 ` Stroller
2014-02-11 0:12 ` Stroller
2014-02-11 0:28 ` Kerin Millar
2014-02-11 1:23 ` Walter Dnes
2014-02-11 2:11 ` Kerin Millar
2014-02-11 2:50 ` Mike Gilbert
2014-02-11 5:41 ` Alan McKinnon
2014-02-11 5:32 ` Alan McKinnon
2014-02-11 11:07 ` Walter Dnes
2014-02-11 11:12 ` Neil Bothwick [this message]
2014-02-11 12:14 ` Alan McKinnon
2014-02-10 19:40 ` Kerin Millar
2014-02-10 19:45 ` [gentoo-user] " eroen
2014-02-10 18:45 ` [gentoo-user] " Alan McKinnon
2014-02-10 20:30 ` Kerin Millar
2014-02-11 1:03 ` Kerin Millar
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=20140211111241.6b5caf11@digimed.co.uk \
--to=neil@digimed.co.uk \
--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