| View previous topic :: View next topic |
| Author |
Message |
Trapamoosch
Apprentice
Joined: 08 May 2004
Posts: 203
|
 Posted: Mon Sep 04, 2006 7:06 pm Post subject: [Portage] Logger les ewarn, possible ? (résolu) |
 |
|
Bonsoir à tous,
J'ai récemment mis à jour OpenSSL, et j'ai pu voir ceci :
| Code: | * You must re-compile all packages that are linked against
* OpenSSL 0.9.7 by using revdep-rebuild from gentoolkit:
* # revdep-rebuild --library libssl.so.0.9.7
* # revdep-rebuild --library libcrypto.so.0.9.7
* After this, you can delete /usr/lib/libssl.so.0.9.7
* and /usr/lib/libcrypto.so.0.9.7 |
Je sais que pas mal d'autres ebuild préviennent l'utilisateur de devoir faire telle ou telle manip. Sauf que quand on n'est pas devant le PC a regarder la console défiler, on rate facilement quelque chose (et qui reste devant la console à regarder tout défiler lors d'une maj ?).
La question qui tue : y'a-t-il un moyen de logger tous les ewarn afin de pouvoir potasser ça tranquillement une fois la maj finie ?
Last edited by Trapamoosch on Mon Sep 04, 2006 7:29 pm; edited 1 time in total |
|
| Back to top |
|
 |
kwenspc
Advocate
Joined: 21 Sep 2003
Posts: 4954
|
| Posted: Mon Sep 04, 2006 7:16 pm Post subject: |
|
|
ben soit tu rediriges la sortie vers un fichier avec > soit je pense que tu peus récupérer le flux stdout et ne pécho que ce que tu souhaite (via un filtre tout con). Cela dit je pense que le plus simple reste encore de chopper la sortie directement.
un ptit emerge world > log_emerge hop et après un grep "* " log_emerge devrait faire l'affaire non? (peut-être faut-il affiner le grep via une regexp au pire)
_________________
membre officieux du SAV Ati GEntoo |
|
| Back to top |
|
|
billiob
Guru
Joined: 30 Dec 2004
Posts: 425
Location: Paris, France
|
| Posted: Mon Sep 04, 2006 7:18 pm Post subject: |
|
|
Ce qui serait exceptionnel, c'est avoir un système un peu comme les mis-à-jour des configs.
A la fin d'un emerge (world, systeme, dès qu'il y a plusieurs paquets), avoir un truc du genre :
You have 5 "things" to do.
Et avoir un utilitaire du genre de dispatch-conf où on verrait quelles sont les "choses" à faire avec possibilité de zapper les "todo", ou de dire qu'on les a fait, ou qu'on s'en fout.
Car quand on fait un emerge -auD world après 2 mois, y a pas mal de paquets qui passent, et on pert pas mal d'infos.
_________________
billiob |
|
| Back to top |
|
|
Trapamoosch
Apprentice
Joined: 08 May 2004
Posts: 203
|
| Posted: Mon Sep 04, 2006 7:19 pm Post subject: |
|
|
Wai tout bêtement, j'y avais me pas pensé tellement c'est simple.
Ceci dit, étonnant que Portage ne gère pas un log, ça serait plutot pratique. |
|
| Back to top |
|
|
geekounet
Bodhisattva
Joined: 11 Oct 2004
Posts: 3772
Location: Wellington, Aotearoa
|
| Posted: Mon Sep 04, 2006 7:27 pm Post subject: |
|
|
| /etc/make.conf.example: | # logging related variables:
# PORTAGE_ELOG_CLASSES: selects messages to be logged, possible values are:
# info, warn, error, log
# Warning: commenting this will disable elog
PORTAGE_ELOG_CLASSES="warn error log"
# PORTAGE_ELOG_SYSTEM: selects the module(s) to process the log messages. Modules
# included in portage are (empty means logging is disabled):
# save (saves one log per package in $PORT_LOGDIR/elog,
# /var/log/portage/elog if $PORT_LOGDIR is unset)
# custom (passes all messages to $PORTAGE_ELOG_COMMAND)
# syslog (sends all messages to syslog)
# mail (send all messages to the mailserver defined
# in $PORTAGE_ELOG_MAILURI)
# To use elog you should enable at least one module
#PORTAGE_ELOG_SYSTEM="save mail"
# PORTAGE_ELOG_COMMAND: only used with the "custom" logging module. Specifies a command
# to process log messages. Two variables are expanded:
# ${PACKAGE} - expands to the cpv entry of the processed
# package (see $PVR in ebuild(5))
# ${LOGFILE} - absolute path to the logfile
# Both variables have to be quoted with single quotes
#PORTAGE_ELOG_COMMAND="/path/to/logprocessor -p '\${PACKAGE}' -f '\${LOGFILE}'"
# PORTAGE_ELOG_MAILURI: this variable holds all important settings for the mail
# module. In most cases listing the recipient address and
# the receiving mailserver should be sufficient, but you can
# also use advanced settings like authentication or TLS. The
# full syntax is:
# address [[user:passwd@]mailserver[:port]]
# where
# address: recipient address
# user: username for smtp auth (defaults to none)
# passwd: password for smtp auth (defaults to none)
# mailserver: smtp server that should be used to deliver the mail (defaults to localhost)
# alternatively this can also be a the path to a sendmail binary if you don't want to use smtp
# port: port to use on the given smtp server (defaults to 25, values > 100000 indicate that starttls should be used on (port-100000))
# Examples:
#PORTAGE_ELOG_MAILURI="root@localhost localhost" (this is also the default setting)
#PORTAGE_ELOG_MAILURI="user@some.domain mail.some.domain" (sends mails to user@some.domain using the mailserver mail.some.domain)
#PORTAGE_ELOG_MAILURI="user@some.domain user:secret@mail.some.domain:100465" (this is left uncommented as a reader excercise ;)
# PORTAGE_ELOG_MAILFROM: you can set the from-address of logmails with this variable,
# if unset mails are sent by "portage" (this default may fail
# in some environments).
#PORTAGE_ELOG_MAILFROM="portage@some.domain"
# PORTAGE_ELOG_MAILSUBJECT: template string to be used as subject for logmails. The following
# variables are exanded:
# ${PACKAGE} - see description of PORTAGE_ELOG_COMMAND
# ${HOST} - FQDN of the host portage is running on
#PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"
|
 |
|
| Back to top |
|
|
Trapamoosch
Apprentice
Joined: 08 May 2004
Posts: 203
|
| Posted: Mon Sep 04, 2006 7:28 pm Post subject: |
|
|
J'aime quand les gens me mettent ma totale ignorance en face des yeux 
En tout cas merci, je vais regarder à ça ! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
French
