From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] PORTAGE_ELOG
Date: Tue, 31 Oct 2006 14:42:33 +0000 [thread overview]
Message-ID: <20061031144233.72ad43c8@krikkit.digimed.co.uk> (raw)
In-Reply-To: <45475849.9090205@ilievnet.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Tue, 31 Oct 2006 16:06:01 +0200, Daniel Iliev wrote:
> Now. The things got even more weird and unexplainable for me. I did
> "emerge -DuNav world" and there were some font packages to be rebuild
> because of a change in the USE flags. After emerge finished I got emails
> for the those packages but not a single message in the syslog. Another
> thing I noticed is that packages emerged by "emerge -DuNav world" put
> their logs in "/var/log/portage/elog/" while all other packages put
> their logs in "/var/log/portage/".
All logs go into $PORT_LOGDIR (usually /var/log/portage) if it is
defined. These are the full output of each emerge command, plus another
file containing the elog/ewarn/einfo/error output. The ELOG files contain
only the e-messages you specify and go in $PORT_LOGDIR/elog. So you
should be seeing logfiles in both if everything is working correctly.
Note that not all ebuilds output e-messages, so you won't get ELOG info
for every package you emerge.
--
Neil Bothwick
- We are but packets in the internet of Life-
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-31 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 20:28 [gentoo-user] PORTAGE_ELOG Daniel Iliev
2006-10-31 8:59 ` Arnau Bria
2006-10-31 14:06 ` Daniel Iliev
2006-10-31 14:15 ` Bo Ørsted Andresen
2006-10-31 14:39 ` Daniel Iliev
2006-10-31 14:42 ` Neil Bothwick [this message]
2006-10-31 15:18 ` [gentoo-user] drift: cron, emerge and mail Daniel Iliev
2006-11-01 12:04 ` Neil Bothwick
2006-11-01 13:15 ` [gentoo-user] [SOLVED] " Daniel Iliev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061031144233.72ad43c8@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox