| View previous topic :: View next topic |
| Author |
Message |
metal_dragen
n00b
Joined: 01 Feb 2003
Posts: 24
Location: Indianapolis, IN
|
 Posted: Wed Feb 19, 2003 11:42 am Post subject: Where are emerge log files saved? |
 |
|
I may have missed this in some of the docs on the site, but can someone tell me where the log files for emerges are? Or if there are even log files. And if not, can logging be turned on? I've been having a hell of a time trying to get gnome and kde installed. Neither will merge correctly.
KDE crashes while merging qt, and so does gnome (i have no idea why gnome needs qt though).
But, anyway, I need to find this log so I can submit a bug report.
Thanks for the help,
metal
_________________
Your lucky number is: 6549871346761673167461.
Watch for it everywhere. |
|
| Back to top |
|
 |
Exci
Apprentice
Joined: 12 Jul 2002
Posts: 265
Location: The Netherlands, Zoetermeer
|
| Posted: Wed Feb 19, 2003 12:45 pm Post subject: |
|
|
| Code: | | /var/log/emerge.log |
but i;m not sure if you find what you are looking for there
you can redirect output to a file
| Code: |
emerge foobar > foobar.txt
|
or only the errors:
| Code: |
emerge foobar 2> foobar.txt
|
|
|
| Back to top |
|
|
metal_dragen
n00b
Joined: 01 Feb 2003
Posts: 24
Location: Indianapolis, IN
|
| Posted: Wed Feb 19, 2003 1:28 pm Post subject: |
|
|
Thanks for the reply. I found the emerge.log file, but it only shows the original command and the time it was issued, ie:
I was hoping that there was a way to get portage to automatically log the output of all merges. I had wanted to avoid output redirection. I've done this in the past, but it ties up my system for about 30 minutes before it crashes out on the aforementioned packages.
Thanks again for the quick reply,
metal
_________________
Your lucky number is: 6549871346761673167461.
Watch for it everywhere. |
|
| Back to top |
|
|
axxackall
l33t
Joined: 06 Nov 2002
Posts: 651
Location: Toronto, Ontario, 3rd Rock From Sun
|
| Posted: Wed Feb 19, 2003 2:42 pm Post subject: |
|
|
In /etc/make.conf you should uncomment this line:
| Code: | | PORT_LOGDIR=/var/log/emerge |
Then create that folder. then enjoy watching all you emerge logs (full) in that folder in separate files  |
|
| Back to top |
|
|
metal_dragen
n00b
Joined: 01 Feb 2003
Posts: 24
Location: Indianapolis, IN
|
| Posted: Wed Feb 19, 2003 4:01 pm Post subject: |
|
|
axxackall - thanks much. you saved the day. can't wait to get home and do that.
i'll have to remember to set cron up to do a periodic cleaning on that directory or it could get unreasonably large. 
_________________
Your lucky number is: 6549871346761673167461.
Watch for it everywhere. |
|
| Back to top |
|
|
axxackall
l33t
Joined: 06 Nov 2002
Posts: 651
Location: Toronto, Ontario, 3rd Rock From Sun
|
| Posted: Wed Feb 19, 2003 11:05 pm Post subject: |
|
|
Be careful with "batching" ebuild processes. Some programs (for example "guile" if I remember) are based on "readline" and their ebuild can either stuck or fail without a real TTY, if you redirect all STDIN.
Another potential problem can be illustrated with "Zope", when you are trying "ebuild zope*.ebuild config" it will stuck (detain), b/c the script is asking you for the username. Even with real TTY, if you allowed LOG in make.conf it will wait your answer without typing the question on the screen. |
|
| Back to top |
|
|
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Sun Feb 23, 2003 4:18 am Post subject: |
|
|
| axxackall wrote: | Be careful with "batching" ebuild processes. Some programs (for example "guile" if I remember) are based on "readline" and their ebuild can either stuck or fail without a real TTY, if you redirect all STDIN.
Another potential problem can be illustrated with "Zope", when you are trying "ebuild zope*.ebuild config" it will stuck (detain), b/c the script is asking you for the username. Even with real TTY, if you allowed LOG in make.conf it will wait your answer without typing the question on the screen. |
Hi,
The new zope-2.6.0-r2 works a bit different now, but it still might have the same issues. How would you suggest fixing this?
_________________
--Kutsuya |
|
| Back to top |
|
|
axxackall
l33t
Joined: 06 Nov 2002
Posts: 651
Location: Toronto, Ontario, 3rd Rock From Sun
|
| Posted: Sun Feb 23, 2003 5:12 am Post subject: |
|
|
| kutsuya wrote: | | The new zope-2.6.0-r2 works a bit different now, but it still might have the same issues. How would you suggest fixing this? |
Let me improvise... Let's put the sample with answers into some config file (will /etc/env.d/zope work for it?). Then let's advise ("ebuild postinst") to users to edit such file and to run "ebuild config" after that. Then "ebuild config" should use that file, being implemented with "expect" if needed (I want to use it for CPAN's dev-perl/Templete-Toolkit). I guess, in case of Zope, Python script will handle it nice.
Of course, if a set of questions depends on the particular system configuration, then "ebuild postinst" should scan the system at first, decide what questions (err... variables) to put into config sample, so the user will answer only appropriate questions (err... will edit apropriate variables).
For case of passwords, "ebuild config" can wipe (or encrypt) the password after reading it from the config sample. Or wipe (delete) the whole sample config after generation the real (final) config file.
In my whole life the only case I've met where a real interactive human user was needed (sort of) for installation was the case of PGP key generation: you type randomly to make sure that your answer is absoltely unrelated to the current system. In all other cases the installation was deterministic enough for being scriptized, using "expect" sometimes when needed. |
|
| Back to top |
|
|
kallamej
Administrator
Joined: 27 Jun 2003
Posts: 4975
Location: Gothenburg, Sweden
|
|
| Back to top |
|
|
|
Duplicate Threads
