Hi,
in SEE region we use pakiti. What pakiti is actually doing is the
following:
There is a client installed in each node and it can be configured
to find the needed updates by either apt or yum. After determining
what is installed and what needs to be installed it reports to a
pakiti server where the the administrator can view all these in a
nice web interface
Regards,
Christos
On Oct 30, 2007, at 1:20 PM, Jan Kundrát wrote:
> Hi,
> we used to have automatic updates enabled at our site, but due to some
> disappointments with upgrade procedure of various critical packages
> (update resulting in DB corruption and other funny stuff), we have
> decided to turn them off so now we update manually.
>
> This has one big disadvantage -- we don't get the security updates
> immediately applied. So I wonder -- is there any utility in SL(C)3 and
> SL(C)4 that enables you to check for security updates? Are the RPMs
> that
> fix security issues somehow tagged in the apt/yum repository?
>
> I've read the documentation of pakiti [1], but I wasn't able to
> find out
> *how* it determines what packages are security updates.
>
> I'm not much familiar with RPM package format, I prefer other
> distribution for non-grid work, so this might be pretty lame question.
> On the other hand, I've tried searching and wasn't able to come up
> with
> a decent answer, so I hope I'll get a reasonable answer here.
>
> [1] http://pakiti.sourceforge.net/
>
> Thanks in advance,
> J. Kundrat
|