From: mRyOuNg <mryoung@soundbomb.net>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Managing multiple servers.
Date: Thu, 26 May 2011 00:24:53 +0200 [thread overview]
Message-ID: <4DDD81B5.5090505@soundbomb.net> (raw)
In-Reply-To: <4DDD6293.3060202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On 05/25/2011 10:12 PM, Kristjan Kalder wrote:
> Is the glsa-check database (or from where it gets its information)
> updated on a regular basis or how does it work?
> If I run the 'glsa-check -t affected' it newer shows me anything.
>
Il I remember well, glsa infos are stored in /usr/portage (metadata or
something)...
glsa-check -t affected should list all unsecure packages...
glsa are updated directly into portage repository, by GLSA team ...
So If GLSA team have infos about an unsecure package, you should be
informed with glsa-check... and a regular emerge --sync...
However, GLSA team seems really busy as there's no new GLSA since
sometimes now ...
To me, I know I love the way Gentoo is working, and the portage
customization (use flags and such) ... but I don't upgrade my packages
so oftenly ... mainly because of time issue.
Something like, every month for my desktops, and every 3/6 months for my
servers ... and due to this, I'm a bit worried about the fact that GLSA
team doesn't give recent updates about security issues...
Anyway, I still sync everyday, and run glsa-check -m affected just to be
sure :)
Cya
[-- Attachment #2: Type: text/html, Size: 1709 bytes --]
next prev parent reply other threads:[~2011-05-25 23:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 22:12 [gentoo-server] Managing multiple servers la Bigmac
2011-05-23 23:11 ` Mark Shields
2011-05-24 0:20 ` Stefan Behte
2011-05-25 18:43 ` Nils
2011-05-25 19:09 ` Kristjan Kalder
2011-05-25 19:27 ` mRyOuNg
2011-05-25 20:12 ` Kristjan Kalder
2011-05-25 22:24 ` mRyOuNg [this message]
2011-05-26 9:30 ` Christian Kauhaus
2011-05-27 14:00 ` Stefan Behte
2011-05-25 20:14 ` Stéphane Guedon
2011-05-25 20:01 ` [gentoo-server] Best backup service? Kristjan Kalder
2011-05-25 20:16 ` Jeff Rooney
2011-05-25 20:17 ` Denis Bondar
2011-05-25 21:33 ` John Lowry
2011-05-25 21:10 ` flockmock
2011-05-25 21:40 ` Homer Parker
2011-05-26 3:53 ` R. David Murray
2011-05-26 4:50 ` Kristjan Kalder
2011-05-26 6:00 ` AW: " Zemke, Kai
2011-05-26 6:09 ` Patrick Nagel
2011-05-26 18:01 ` R. David Murray
2011-05-26 11:33 ` Konstantin
2011-05-26 12:30 ` nirn
2011-05-30 15:54 ` [gentoo-server] Managing multiple servers Jean-François Maeyhieux
2011-06-02 19:31 ` Sven Vermeulen
2011-06-02 20:33 ` David
2011-06-03 9:37 ` Christian Kauhaus
2011-06-03 10:49 ` Joost Roeleveld
2011-06-03 13:24 ` Christian Kauhaus
2011-05-24 0:40 ` kashani
2011-05-24 2:44 ` Fabiano - deStilaDo
2011-05-24 5:32 ` Pandu Poluan
2011-05-24 11:50 ` Fabiano - deStilaDo
2011-05-24 1:12 ` kashani
2011-05-24 12:47 ` Matthew Marlowe
2011-05-24 7:37 ` Ramon van Alteren
2011-05-24 8:21 ` Pandu Poluan
2011-05-24 9:19 ` Robert Bridge
2011-05-24 10:11 ` Pandu Poluan
2011-05-24 16:04 ` kashani
2011-05-24 14:06 ` Ramon van Alteren
2011-05-24 12:40 ` Hacking Network Solutions - Gentoo List Subscriptions
2011-05-24 14:45 ` Christian Kauhaus
2011-05-24 15:36 ` Dawid Węgliński
2011-05-24 21:06 ` Ramon van Alteren
2011-05-25 16:16 ` Christian Kauhaus
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 1:31 Pandu Poluan
2011-05-24 11:26 Fabiano - deStilaDo
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=4DDD81B5.5090505@soundbomb.net \
--to=mryoung@soundbomb.net \
--cc=gentoo-server@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