1 |
or to reduce bandwidth try this as the crontab command: |
2 |
|
3 |
rsync --recursive --links --safe-links --perms --times --compress |
4 |
--force --whole-file --delete --delete-after --stats --timeout=180 |
5 |
rsync://rsync.gentoo.org/gentoo-portage/metadata/glsa/* /usr/portage/metadata/glsa/ ;glsa-check -n -l|grep "\[N" |
6 |
|
7 |
This syncs only the glsa metadata, and the cron email also shows updates |
8 |
that it has synced, but do not apply to your system. However, when you |
9 |
do a glsa -f package to apply the fix, you must first "emerge sync" to |
10 |
update the full tree. As glsa's that affect my systems are few and far |
11 |
between, there's quite a bandwidth saving. |
12 |
|
13 |
e.g., |
14 |
|
15 |
___________________ |
16 |
... |
17 |
|
18 |
MOTD brought to you by motd-o-matic, version 0.3 |
19 |
|
20 |
receiving file list ... done |
21 |
glsa-200509-03.xml |
22 |
timestamp.chk |
23 |
|
24 |
Number of files: 539 |
25 |
Number of files transferred: 2 |
26 |
Total file size: 1406439 bytes |
27 |
Total transferred file size: 2153 bytes |
28 |
Literal data: 2153 bytes |
29 |
Matched data: 0 bytes |
30 |
File list size: 8682 |
31 |
Total bytes written: 199 |
32 |
Total bytes read: 11353 |
33 |
|
34 |
wrote 199 bytes read 11353 bytes 2100.36 bytes/sec |
35 |
total size is 1406439 speedup is 121.75 |
36 |
WARNING: This tool is completely new and not very tested, so it should |
37 |
not be |
38 |
used on production systems. It's mainly a test tool for the new GLSA |
39 |
release |
40 |
and distribution system, it's functionality will later be merged into |
41 |
emerge |
42 |
and equery. |
43 |
Please read http://www.gentoo.org/proj/en/portage/glsa-integration.xml |
44 |
before using this tool AND before reporting a bug. |
45 |
|
46 |
[N] indicates that the system might be affected. |
47 |
|
48 |
|
49 |
___________________ |
50 |
In the above case, a new glsa (glsa-200509-03) has been issued, but it |
51 |
doesnt apply. On my todo list is to filter and summarize so all I get |
52 |
is whats new, and what applies to me! |
53 |
|
54 |
BillK |
55 |
|
56 |
|
57 |
On Tue, 2005-09-06 at 23:12 -0700, Michael Irey wrote: |
58 |
> To make it easy I have added these 2 lines to my crontab |
59 |
> |
60 |
> 10 2 * * * /usr/bin/emerge --sync 2> /dev/null |
61 |
> > /root/tmp/daily-emerge-sync.txt |
62 |
> 50 2 * * * /usr/bin/glsa-check -ln 2> /dev/null | grep ' \[N\]' |
63 |
> |
64 |
> Then every morning I get an email if there are packages with vulnerabilities. |
65 |
> |
66 |
> I can decide manually the priority. Because I dont want apache updating |
67 |
> itself in the middle of the night... I do it manually, from my emailed list. |
68 |
> |
69 |
> |
70 |
> On Tuesday 06 September 2005 02:53 pm, Jeremy Brake wrote: |
71 |
> > Hey, |
72 |
> > |
73 |
> > Is there anything in Portage which will allow me to view security |
74 |
> > updates, seperate from general version updates? |
75 |
> > At the moment i have a 5am cron job which runs "emerge --sync && emerge |
76 |
> > -upvD world" , and i just glance at it as soon as I i sit down at my pc |
77 |
> > for the day. |
78 |
> > The problem here is that I cant tell if updates (eg, at the moment it |
79 |
> > wants to update openssh and apache2) are security patches, or just |
80 |
> > general version upgrades. |
81 |
> > |
82 |
> > I know i can use "system" instead of "world" and omit the -D option, but |
83 |
> > thats not targeting my issue exactly. Is there a way to see which |
84 |
> > updates are security patches, without having to manually trawl through |
85 |
> > webpages and changelogs? |
86 |
> > |
87 |
> > Jeremy |
88 |
-- |
89 |
gentoo-server@g.o mailing list |