| View previous topic :: View next topic |
| Author |
Message |
Kasumi_Ninja
Veteran
Joined: 18 Feb 2006
Posts: 1825
Location: The Netherlands
|
 Posted: Fri Dec 21, 2007 10:38 pm Post subject: Is glsa-check -m affected a good way to check a system? |
 |
|
I wonder if "glsa-check -m affected" is the right way to check automatically -and receive a mail- if your system is affected by any (recent) glsa? Normally I would use "glsa-check -t all". Is there any difference?
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered |
|
| Back to top |
|
 |
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Sat Dec 22, 2007 5:55 am Post subject: |
|
|
i use "-n -l affected", seems to be okay for me. ymmv ofc. 
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
Suicidal
l33t
Joined: 30 Jul 2003
Posts: 959
Location: /dev/null
|
| Posted: Sat Dec 22, 2007 6:43 am Post subject: |
|
|
I used to use something like:
| Code: | | glsa-check --list all | grep "[[ N ]]" | mail -s "glsa-check for $HOSTNAME" foo@bar.com |
Sadly I currently don't have any Gentoo servers at my new job.  |
|
| Back to top |
|
|
Kasumi_Ninja
Veteran
Joined: 18 Feb 2006
Posts: 1825
Location: The Netherlands
|
| Posted: Sat Dec 22, 2007 10:34 am Post subject: |
|
|
| bunder wrote: | | i use "-n -l affected", seems to be okay for me. ymmv ofc. |
When I issue a "glsa-check -t -m all" I get:
| Code: | please use only one command per call
Syntax: glsa-check <option> [glsa-list] |
| Suicidal wrote: | I used to use something like:
| Code: | | glsa-check --list all | grep "[[ N ]]" | mail -s "glsa-check for $HOSTNAME" foo@bar.com |
Sadly I currently don't have any Gentoo servers at my new job. |
Thanks, I might use that only I was hoping that glsa-check has a similar feature build in 
P.S.
No Gentoo servers?! Time to find a new job 
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5934
|
| Posted: Sat Dec 22, 2007 1:24 pm Post subject: |
|
|
| Aniruddha wrote: | | bunder wrote: | | i use "-n -l affected", seems to be okay for me. ymmv ofc. |
When I issue a "glsa-check -t -m all" I get:
| Code: | please use only one command per call
Syntax: glsa-check <option> [glsa-list] |
|
not sure what's causing that... but i also use glsa-check from within cron, which makes -m unneeded.
cheers
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
Kasumi_Ninja
Veteran
Joined: 18 Feb 2006
Posts: 1825
Location: The Netherlands
|
| Posted: Sat Dec 22, 2007 2:45 pm Post subject: |
|
|
| bunder wrote: | | Aniruddha wrote: | | bunder wrote: | | i use "-n -l affected", seems to be okay for me. ymmv ofc. |
When I issue a "glsa-check -t -m all" I get:
| Code: | please use only one command per call
Syntax: glsa-check <option> [glsa-list] |
|
not sure what's causing that... but i also use glsa-check from within cron, which makes -m unneeded.
cheers |
Great! That is exactly what I want to do. Can you post your crontab entry for glsa-check?
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered |
|
| Back to top |
|
|
|
Networking & Security
