Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Log of emerge readable output produced somewhere?
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4  
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
ruivilela
Apprentice
Apprentice


Joined: 05 Oct 2004
Posts: 236
Location: Łódź

PostPosted: Mon Oct 16, 2006 9:39 am    Post subject: Reply with quote

I just tryed reemerging something and later parsed the file. :)

Added solved. Thanks
Back to top
View user's profile Send private message
nixnut
Bodhisattva
Bodhisattva


Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains

PostPosted: Mon Oct 16, 2006 3:59 pm    Post subject: Reply with quote

Merged 5 previous posts here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand
Back to top
View user's profile Send private message
Crono81
Tux's lil' helper
Tux's lil' helper


Joined: 07 Nov 2006
Posts: 86

PostPosted: Thu Nov 23, 2006 1:22 pm    Post subject: Reply with quote

I only want to see the * BLA BLA and * BLA BLA informations of an ebuild, having it installed or not. How to do that?
Back to top
View user's profile Send private message
Wooff
Tux's lil' helper
Tux's lil' helper


Joined: 19 Jun 2004
Posts: 101
Location: LB.CZ.EU

PostPosted: Thu Nov 23, 2006 1:43 pm    Post subject: human readable format of TIME in emerge.log Reply with quote

hi,
I would like to force portage to use any human readable format for DATE and TIME . Any idea?

for example anything like this:
Code:
2006/11/24 14:40:38  >>> emerge (1 of 1) net-ftp/ftp-0.17-r6 to /
2006/11/24 14:41:16  *** exiting successfully.

instead of
Code:
1164288247:  >>> emerge (1 of 1) net-ftp/ftp-0.17-r6 to /
1164288271:  *** exiting successfully.
Back to top
View user's profile Send private message
tomk
Administrator
Administrator


Joined: 23 Sep 2003
Posts: 7219
Location: Sat in front of my computer

PostPosted: Thu Nov 23, 2006 8:08 pm    Post subject: Reply with quote

Maybe this topic is of use: nice trick: formatting the time code in emerge.log.
_________________
Search | Read | Answer | Report | Strip
Back to top
View user's profile Send private message
lenkki
n00b
n00b


Joined: 03 Mar 2004
Posts: 55

PostPosted: Sat Dec 02, 2006 1:49 pm    Post subject: Reply with quote

Why aint elog save enabled by default in the make config and when an emerge is finnished just automatically echo the saved contents to the user? Isn't this what most users want? To actually see the important warnings/info for each package without having to watch the compile. To me it seems as all the required code for doing this is in place allready. The additions to the emerge script shouldn't be that overwhelming, to my understanding.

edit: I'm writing this because I in my last emerge -uD world by pure luck managed to catch an einfo message from GTK telling me to rebuild certain packages because they would break else. Why in the name of $DEITY is so important information allowed to just scroll by in useless compile output? For the record this wouldn't have been the first time my gentoo system got b0rken by an -uD world, and yes I _ALLWAYS_ run etc-update after my updates, regardless of if I was told or not.
Back to top
View user's profile Send private message
bLUEbYTE84
Guru
Guru


Joined: 21 Jul 2006
Posts: 566
Location: universe.tar.gz, src/earth.h, struct homo_sapiens_table

PostPosted: Wed Dec 06, 2006 7:51 pm    Post subject: Reply with quote

lenkki wrote:
Why aint elog save enabled by default in the make config and when an emerge is finnished just automatically echo the saved contents to the user? Isn't this what most users want? To actually see the important warnings/info for each package without having to watch the compile. To me it seems as all the required code for doing this is in place allready. The additions to the emerge script shouldn't be that overwhelming, to my understanding.


Agreed.

Crono81 wrote:
I only want to see the * BLA BLA and * BLA BLA informations of an ebuild, having it installed or not. How to do that?


I also would like to know how to do precisely this.
Back to top
View user's profile Send private message
jphein
n00b
n00b


Joined: 17 Apr 2006
Posts: 3

PostPosted: Wed Jan 10, 2007 8:20 am    Post subject: This is what I have found. Reply with quote

It looks like this is now in portage.

You just need to add some variables to your make.conf
Code:

# This sets where to log
PORT_LOGDIR=/var/log/portage
# This sets what to log
PORTAGE_ELOG_CLASSES="warn error log info"
# And this is how to do it
PORTAGE_ELOG_SYSTEM="save"

You may need to create the directories
Code:

mkdir /var/log/portage
mkdir /var/log/portage/elog


GUIs for viewing the "elogs" are available in portage: http://packages.gentoo.org/search/?sstring=elogs
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2867
Location: Omnipresent

PostPosted: Sun Jan 14, 2007 12:14 am    Post subject: Reply with quote

What exactly do the various elog classes mean? The sample conf and documentation are vague.

I presume that info, warn and error record the respective einfo/ewarn/eerror messages to the individual elogs. What does log do?
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
_pF_
Apprentice
Apprentice


Joined: 22 Apr 2004
Posts: 195
Location: Central London

PostPosted: Sun Jan 14, 2007 6:33 pm    Post subject: Invisible linux-headers mystery. Reply with quote

Having emerged linux-headers, I was fortunate to see a notice's recommending a rebuild of glibc appear on the screen. Checking elogv and kelogviewer, though, I see no mention at all of linux-headers, let alone its messages. These two programs both show all of the other contemporaneous emerges, just not linux-headers.
Back to top
View user's profile Send private message
Hypnos
Advocate
Advocate


Joined: 18 Jul 2002
Posts: 2867
Location: Omnipresent

PostPosted: Mon Jan 15, 2007 12:34 am    Post subject: Reply with quote

Nevermind my question two posts above -- it's in the devmanual.
_________________
Personal overlay | Simple backup scheme
Back to top
View user's profile Send private message
Bones McCracker
Veteran
Veteran


Joined: 14 Mar 2006
Posts: 1565
Location: U.S.A.

PostPosted: Mon Jan 15, 2007 5:38 pm    Post subject: Reply with quote

Several people seem to be looking for a way to keep /var/log/portdir clean.
Just wanted to point out that the tmpwatch serves this purpose well and is very simple to configure.
Code:
# emerge tmpwatch

It installs the 15 KB binary /usr/sbin/tmpwatch, and it creates a little bourne script in /etc/cron.daily. There is no configuration file.

Add this line to the variables section near the top. You could manually assign PORT_LOGDIR (or just type /var/log/portage directly in the rule), but this will query portage to dynamically determine the correct location of its log directory so the script will still function if you change the log location:
Code:
PORT_LOGDIR="$(portageq envvar PORT_LOGDIR)"

Then down below, add a rule something like this to clean the portage log directory (delete the files that have not been modified in >=168 hours):
Code:
${TMPWATCH} --mtime 168 $PORT_LOGDIR

Alternative: If you want, you can exclude your elog directory like so (instead of line above):
Code:
${TMPWATCH} --exclude $PORT_LOGDIR/elog --mtime 168 $PORT_LOGDIR

Option: If so, and you still want to clean elog but after a different time, you could then insert a second rule below the first to handle it:
Code:
${TMPWATCH} --mtime 720 $PORT_LOGDIR/elog
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2493
Location: The Peanut Gallery

PostPosted: Fri Jan 19, 2007 5:13 am    Post subject: Reply with quote

Man that is nice! I'm adding this to my tips if that's ok BoneKracker?

Can this also be used to keep distfiles clean and is there more config? (I know, RTFM ;)
Back to top
View user's profile Send private message
Bones McCracker
Veteran
Veteran


Joined: 14 Mar 2006
Posts: 1565
Location: U.S.A.

PostPosted: Fri Jan 19, 2007 4:35 pm    Post subject: Reply with quote

Go for it. :)

Yeah, you'll be pleased to know it comes already configured to clean distfiles and the portage tempdir. I primarily use a monthly eclean for that, but have tmpwatch sweeping up any remaining cruft months later.
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 2493
Location: The Peanut Gallery

PostPosted: Sun Jan 21, 2007 3:25 am    Post subject: Reply with quote

BoneKracker wrote:
Yeah, you'll be pleased to know it comes already configured to clean distfiles and the portage tempdir. I primarily use a monthly eclean for that, but have tmpwatch sweeping up any remaining cruft months later.
Loverley!
Back to top
View user's profile Send private message
OneOfMany
Tux's lil' helper
Tux's lil' helper


Joined: 19 Nov 2003
Posts: 108
Location: Portland, OR USA

PostPosted: Fri Aug 31, 2007 12:37 pm    Post subject: Re: This is what I have found. Reply with quote

jphein wrote:
It looks like this is now in portage.

You just need to add some variables to your make.conf
Code:

# This sets where to log
PORT_LOGDIR=/var/log/portage
# This sets what to log
PORTAGE_ELOG_CLASSES="warn error log info"
# And this is how to do it
PORTAGE_ELOG_SYSTEM="save"

You may need to create the directories
Code:

mkdir /var/log/portage
mkdir /var/log/portage/elog


GUIs for viewing the "elogs" are available in portage: http://packages.gentoo.org/search/?sstring=elogs

Where would a user figure out they need to make an elog directory? I mean other than searching here? I happened to know that I could set the log directory to gain more information. And I did read the entry in make.conf.sample (or is it example?) that talks about needing to create the /var/log/portage directory for this to work. But I didn't see anything about needing to make an elog directory too. And without it I get a list of what compiled, but not the after ebuild instructions.

Thankfully I have a new target to search under for this info, but I want to echo the disbelief that I have to manually get the list of things that packages have told me I must do. Things that may totally hose my system if I don't do them before I reboot are lost unless I know the magic handshake(s). Not the best way to make a user friendly system.
Back to top
View user's profile Send private message
Carlo
Developer
Developer


Joined: 12 Aug 2002
Posts: 3356

PostPosted: Sat Mar 01, 2008 5:38 pm    Post subject: Re: This is what I have found. Reply with quote

OneOfMany wrote:
Where would a user figure out they need to make an elog directory? I mean other than searching here?

Well, you can put the log where you're up to, of course. Knowing the FHS and the ideas behind it helps a lot and is basic preconditioned Unix knowledge.
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs.
Back to top
View user's profile Send private message
theSlayer
n00b
n00b


Joined: 15 Aug 2008
Posts: 8

PostPosted: Thu Dec 18, 2008 12:00 pm    Post subject: Reply with quote

Thanks for the idea - till now when I needed to log outputs I used emerge | tee emergelog but it was bad, because output was no longer colourful :-D
Back to top
View user's profile Send private message
passive
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2004
Posts: 105

PostPosted: Sun May 16, 2010 11:50 am    Post subject: Just a thought Reply with quote

Could a mod add something like the following to the first post of this thread?

Quote:

By default, emerge messages are logged here:
/var/log/portage/elog


I had to read 3 pages to find that.
Back to top
View user's profile Send private message
majoron
Apprentice
Apprentice


Joined: 12 Oct 2005
Posts: 191
Location: Frankfurt

PostPosted: Thu Jul 08, 2010 9:04 am    Post subject: about ebuilds messages logging Reply with quote

Hi,
how can I recover the messages displayed by portage after emerging some packages?

I found that you can control this with the PORT_LOGDIR variable, but shouldn't the most important messages be stored by default anywhere for future reference?

I'm sure this question has been asked and answered several times, but I'm not able to find it in the boards.

TIA
_________________
Computers are like air conditioners, they stop working properly if you open Windows
Back to top
View user's profile Send private message
tomk
Administrator
Administrator


Joined: 23 Sep 2003
Posts: 7219
Location: Sat in front of my computer

PostPosted: Thu Jul 08, 2010 9:13 am    Post subject: Reply with quote

Merged previous post.
_________________
Search | Read | Answer | Report | Strip
Back to top
View user's profile Send private message
majoron
Apprentice
Apprentice


Joined: 12 Oct 2005
Posts: 191
Location: Frankfurt

PostPosted: Thu Jul 08, 2010 9:50 am    Post subject: Reply with quote

tomk wrote:
Merged previous post.

Thank you!

I need to improve my search skills...
_________________
Computers are like air conditioners, they stop working properly if you open Windows
Back to top
View user's profile Send private message
archrax
n00b
n00b


Joined: 05 Dec 2011
Posts: 45

PostPosted: Tue Feb 25, 2014 6:34 pm    Post subject: Reply with quote

I have defined
Code:
PORT_LOGDIR='var/log/portage/build'
in
Code:
/etc/portage/make.conf
which is where I get information captured on each build during an emerge.

However, I notice that I am no longer receiving the important summary information in
Code:
/var/log/portage/elog/summary.log
as a result. Is there anyway of getting this back whilst retaining the individual build logs?

thanks
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Goto page Previous  1, 2, 3, 4
Page 4 of 4

 
Jump to:  
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