On Feb 24, 2012 7:06 PM, "Neil Bothwick" wrote:
>
> On Fri, 24 Feb 2012 17:30:23 +0700, Pandu Poluan wrote:
>
> > > It would be worth adding glsa-check to that list. Run it every day
> > > from cron to get mailed about any security risks.
>
> > I'm a bit scared running glsa-check automatically. I
On Fri, 24 Feb 2012 17:30:23 +0700, Pandu Poluan wrote:
> > It would be worth adding glsa-check to that list. Run it every day
> > from cron to get mailed about any security risks.
> I'm a bit scared running glsa-check automatically. I may have
> misunderstood, but my thought is that glsa-check c
On Feb 24, 2012 4:13 PM, "Neil Bothwick" wrote:
>
> On Fri, 24 Feb 2012 11:34:46 +0700, Pandu Poluan wrote:
>
> > The only automation in my case is eix-sync followed by emerge -uND
> > --fetchonly @system @world
>
> It would be worth adding glsa-check to that list. Run it every day from
> cron to
On Fri, 24 Feb 2012 11:34:46 +0700, Pandu Poluan wrote:
> The only automation in my case is eix-sync followed by emerge -uND
> --fetchonly @system @world
It would be worth adding glsa-check to that list. Run it every day from
cron to get mailed about any security risks.
--
Neil Bothwick
Q. Ho
On Feb 24, 2012 7:18 AM, "Harry Putnam" wrote:
>
> First my setup:
>
> Fairly basic (newish) install (noX) in a Virtual Box vm on windows7 host
>
> I'd like to hear some of the ways you all keep up with syncing and
> update world.
>
> Of course the basic call with cron is clear enough:
>
> eix-sy
On Thu, Feb 23, 2012 at 5:52 PM, Harry Putnam wrote:
> First my setup:
>
> Fairly basic (newish) install (noX) in a Virtual Box vm on windows7 host
>
> I'd like to hear some of the ways you all keep up with syncing and
> update world.
I personally run it all manually and never schedule it to run
6 matches
Mail list logo
