On 14/12/16 15:45, Rich Freeman wrote: > On Wed, Dec 14, 2016 at 10:27 AM, M. J. Everitt <[email protected]> wrote: >> I do, but only usually if its the last package of an emerge because >> otherwise its lost many many thousands of lines upwards. Thank goodness >> for portage's savelog feature. - Actually that reminds me .. someone >> mentioned a useful tweak to that, with an appropriate FEATURES switch, >> it would categorise the output of the logging system .. must look that >> one up again, or poke the wiki team ....... >> > IMO, emailing elogs to root should probably be the default. By all > means let people turn it off, but I bet a lot of people don't realize > it is an option. > > This goes in all my make.conf files: > PORTAGE_ELOG_CLASSES="warn error log" > PORTAGE_ELOG_SYSTEM="save mail" > PORTAGE_ELOG_MAILURI="[email protected] smtp.server.address" > PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice" > > Yes, some packages are a bit spammy and this should be fixed, but in > general it has prevented more headaches than it has caused. > I would tend to agree that in a sysadmin role this would be very helpful.
At the risk of repeating myself, is there any einfo/elog displayed when portage is (first) updated, to alert users of this functionality? A link to the wiki page explaining the features [poke wiki team!] mentioned would probably be most useful.
signature.asc
Description: OpenPGP digital signature
