[gentoo-user] elog saves messages in wrong folder

[gentoo-user] elog saves messages in wrong folder

[Marc Blumentritt]

Hi,

on one of my machines elog saves messages in /var/log/portage instead of
/var/log/portage/elog ? The funny thing is, that it worked first.

I'm using a self-made profile. Could this be a problem?


Cheers
Marc



emerge --info
Portage 2.1.1 (!../usr/portage/profiles/epios/2005.01.smp, gcc-4.1.1,
glibc-2.4-r3, 2.6.15-epios-r100 i686)
=================================================================
System uname: 2.6.15-epios-r100 i686 VIA Nehemiah
Gentoo Base System version 1.12.5
Last Sync: Sun, 24 Sep 2006 11:20:02 +0000
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.2.11-r1
dev-lang/python:     2.3.5, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r3
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.17-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=c3-2 -Os -fomit-frame-pointer -pipe -msse -mmmx -mfpmath=sse"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild
/etc/terminfo"
CXXFLAGS="-march=c3-2 -Os -fomit-frame-pointer -pipe -msse -mmmx
-mfpmath=sse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch
sandbox sfperms strict userpriv"
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
http://distfiles.gentoo.org "
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
LINGUAS="de us"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--compress --force --whole-file --delete --delete-after --stats
--timeout=180 --exclude='/distfiles' --exclude='/local'
--exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp/portage"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/my_ebuilds /usr/local/portage/epios
/usr/portage/local/layman/gentoo-de"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="x86 16bit X a52 aac accessibility acpi alsa apm audiofile avi
bash-completion berkdb bitmap-fonts browserplugin bzip2 bzlib caps cddb
cdio cdparanoia cdr cjk cle266 cli crypt curl dbus dga directfb
divx4linux dlloader dri dts dv dvb dvd dvdr dvdread dxr3 elibc_glibc
emboss encode expat ext-doc ext-dvi ext-lyx ext-man ext-openoffice
ext-pdf ext-ppt ext-ps ext-rtf ext-tex ext-xls fbcon ffmpeg flac fortran
gd gdbm gif gnutls gphoto2 gstreamer hal ieee1394 imagemagick imlib
input_devices_keyboard input_devices_mouse isdnlog java javascript
joystick jpeg kernel_linux lcd lcms libcaca libg++ libwww linguas_de
linguas_us lirc lirc_devices_imon live lm_sensors logitech-mouse mad
matroska mikmod mmx mng motif mp3 mpeg mplayer musepack musicbrainz
mysql mysqli mythtv ncurses nls nocd nptl nptlonly nsplugin ogg
oggvorbis opengl pam pcre pdflib perl php png pppd python qt qt3 qt4
quicktime readline real reflection sdl session skey slang smp sndfile
snmp speex spell spl sse ssl streamzap subversion svg tcltk tcpd tetex
theora threads tidy tiff transcode truetype truetype-fonts type1-fonts
udev unichrome unichromepro unicode usb userland_GNU userlocales v4l
v4l2 vcd vdr verbose video_cards_via vidix vlm vorbis wifi win32codecs
wmf xanim xattr xcomposite xine xinerama xml xorg xv xvid xvmc zeroconf
zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_RSYNC_EXTRA_OPTS

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] elog saves messages in wrong folder

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

On Mon, 25 Sep 2006 10:47:36 +0200, Marc Blumentritt wrote:

> on one of my machines elog saves messages in /var/log/portage instead of
> /var/log/portage/elog ? The funny thing is, that it worked first.

Does var/log/portage/elog exist? Is it writable by portage?

$ ls -ld /var/log/portage/elog/
drwxrws--- 2 portage portage 106616 2006-09-25 00:44 /var/log/portage/elog/


-- 
Neil Bothwick

"Give me Liberty, fries, and two cokes to go!" "*CUT!*"

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: elog saves messages in wrong folder

[Marc Blumentritt]

Neil Bothwick schrieb:
> On Mon, 25 Sep 2006 10:47:36 +0200, Marc Blumentritt wrote:
> 
>> on one of my machines elog saves messages in /var/log/portage instead of
>> /var/log/portage/elog ? The funny thing is, that it worked first.
> 
> Does var/log/portage/elog exist? Is it writable by portage?
> 
> $ ls -ld /var/log/portage/elog/
> drwxrws--- 2 portage portage 106616 2006-09-25 00:44 /var/log/portage/elog/

Yes:

ls -ld /var/log/portage/elog/
drwxrws--- 2 portage portage 8192 2006-09-25 09:18 var/log/portage/elog/

Marc




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] elog saves messages in wrong folder

[Richard Fish]

On 9/25/06, Marc Blumentritt <marc.blumentritt@arcor.de> wrote:
> Hi,
>
> on one of my machines elog saves messages in /var/log/portage instead of
> /var/log/portage/elog ? The funny thing is, that it worked first.

What does "grep PORT_LOGDIR /etc/make.conf*" report?

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] elog saves messages in wrong folder

[Philip Webb]

060925 Richard Fish wrote:
> On 9/25/06, Marc Blumentritt <marc.blumentritt@arcor.de> wrote:
>> on one of my machines elog saves messages in /var/log/portage instead of
>> /var/log/portage/elog ? The funny thing is, that it worked first.
> What does "grep PORT_LOGDIR /etc/make.conf*" report?

there are  2  logging procedures in the latest  make.conf.example :

  # PORT_LOGDIR is the location where portage will store all the logs it
  # creates from each individual merge. They are stored as NNNN-$PF.log
  # in the directory specified. This is disabled until you enable it by
  # providing a directory. Permissions will be modified as needed IF the
  # directory exists, otherwise logging will be disabled. NNNN is the
  # increment at the time the log is created. Logs are thus sequential.
  #PORT_LOGDIR=/var/log/portage

and (both are edited to shorten lines)

  # PORTAGE_ELOG_CLASSES: selects msgs 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"

'logdir' used to be populated with lines like

  4332-portage-2.1.1.log
  4333-portage-2.1-r2.log
  4333-portage-2.1.1.log

but since those for update to Portage 2.1.1 , no more have appeared.

'elog' creates lines like

  app-admin:gkrellm-2.2.9-r1:20060923-012928.log
  app-arch:gzip-1.3.5-r8:20060923-011035.log
  app-arch:gzip-1.3.5-r9:20060923-011012.log
  app-arch:zip-2.31-r1:20060923-011114.log

which used to be dropped in a subdir 'elog', but now appear in $PORT_LOGDIR .

Yes, I do still have the appropriate lines in my working  make.conf .

This looks like a bug in the new version of Portage.
Perhaps someone should report it: it's not a high priority for me.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] elog saves messages in wrong folder

[Richard Fish]

On 9/25/06, Philip Webb <purslow@sympatico.ca> wrote:
> This looks like a bug in the new version of Portage.
> Perhaps someone should report it: it's not a high priority for me.

I'm on portage 2.1.2_pre1-r1, and logs are still appearing in
/v/l/portage/elog/ for me.  So I'm really thinking this behavior will
only show up with particular make.conf settings.  Can either of you
post your make.conf please?

-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] elog saves messages in wrong folder

[Philip Webb]

060925 Richard Fish wrote:
> On 9/25/06, Philip Webb <purslow@sympatico.ca> wrote:
> Can either of you post your make.conf please?

You asked (smile):

# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-src/portage/cnf/make.conf.x86,v 1.5 2004/10/10 23:27:28 carpaski Exp $
# Contains local system settings for Portage system

# Please review 'man make.conf' for more information.

# PP 031116

CLEAN_DELAY=10

# Build-time functionality
# ========================
#
# The USE variable is used to enable optional build-time functionality. For
# example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them:  --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-portage/ufed'
#
# Example:
#USE="X gtk gnome -alsa"

# PP 041110 : suppress dft use flags fr  /etc/make.profile/make.defaults :
#  sound (alsa arts avi encode esd mad mikmod oggvorbis oss quicktime xmms)
#  sql (berkdb libg++ mysql postgres) f77 nls
# PP 050501 : '-alsa' added for Gnomelib
# PP 050831 : '-vorbis' added for Mplayer
# PP 050905 : 'usb' added for scanner
# PP 050906 : '-flac -mp3 -ogg -sox' added to remove further sound
# PP 050910 : 'nvidia' added for Nvidia
# PP 051119 : 'pop' added for Mutt
# PP 051204 : '-gnome' added for efficiency
# PP 060320 : 'fam' added for Gamin

#USE="fam nvidia pop usb -alsa -arts -avi -berkdb -encode -esd -flac -f77
#     -gnome -libg++ -mad -mikmod -mp3 -mysql -nls -ogg -oss -postgres
#     -quicktime -sox -vorbis -xmms"

# PP 060507 : reorg'd using 2006.0 & "-*"
# PP 060603 : drop 'pam'
# PP 060701 : add 'nptl nptlonly' for glibc-2.4
# PP 060702 : chg 'qt' -> 'qt3' ('qt' ~ longer valid)
# PP 060705 : drop 'mozilla'
USE="-* apm bitmap-fonts bonobo bzip2 cdr crypt cups dri foomaticdb
     gdbm gif gnutls gpm gtk gtk2 imagemagick imlib java javascript jpeg kde
     libwww lm_sensors mime motif mpeg ncurses nptl nptlonly
     nsplugin nvidia opengl pcre pdf perl plotutils png pop python
     qt3 readline scanner session slang ssl
     tiff truetype truetype-fonts type1-fonts unicode usb X xml xv zlib"

# PP 060915 : add 2 lines for mod-X
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="nv nvidia vesa"

# Host Setting
# ============
#
# Change this line as appropriate (i686, i586, i486 or i386).
# All modern systems (even Athlons) should use "i686-pc-linux-gnu".
# All K6's are i586.
CHOST="i686-pc-linux-gnu"

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
# pentium3, and pentium4.
#
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# CRITICAL WARNINGS: ****************************************************** #
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
# Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. #
# ************************************************************************* #
#
# Decent examples:
#
#CFLAGS="-march=pentium3 -O3 -pipe"
#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CFLAGS="-O2 -march=athlon-xp -pipe" # PP 031008

# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"

# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
#
# Please note that this is not for development, alpha, beta, nor cvs release
# packages. "Broken" packages will not be added to testing and should not be
# requested to be added. Alternative routes are available to developers
# for experimental packages, and it is at their discretion to use them.
#
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
#ACCEPT_KEYWORDS="~arch"

# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
#     temporary storage of data. This can get VERY large depending upon
#     the application being installed.
#PORTAGE_TMPDIR=/var/tmp
PORTAGE_TMPDIR=/z/tmp # PP 031018
#
# PORTDIR is the location of the portage tree. This is the repository
#     for all profile information as well as all ebuilds. This directory
#     itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
#     emerges. The source code is maintained here unless you delete
#     it. The entire repository of tarballs for gentoo is 9G. This is
#     considerably more than any user will ever download. 2-3G is
#     a large DISTDIR.
#DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
#     with '--buildpkg' or '-b' while emerging a package. This can get
#     upto several hundred megs, or even a few gigs.
#PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
#     creates from each individual merge. They are stored as NNNN-$PF.log
#     in the directory specified. This is disabled until you enable it by
#     providing a directory. Permissions will be modified as needed IF the
#     directory exists, otherwise logging will be disabled. NNNN is the
#     increment at the time the log is created. Logs are thus sequential.
# PP 050207
PORT_LOGDIR=/var/log/emerge-logs

#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored
# without concern they wb deleted by rsync updates. Default not defined.
# PP 060310
PORTDIR_OVERLAY=/usr/local/portage

# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Default fetch command (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space separated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
# PP 041114 try by hand : Osuosl is slow, but works :
#GENTOO_MIRRORS="http://gentoo.osuosl.org/"
# PP 051113 : next line generated by Mirrorselect :
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ http://adelie.polymtl.ca/ http://prometheus.cs.wmich.edu/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.seren.com/gentoo"
#
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
# The list is a single entry specifying the full address of the directory
# serving the tbz2's for your system. Running emerge with either '--getbinpkg'
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all
# packages in the directory specified, and use that data to determine what will
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
# consult the man pages and 'emerge --help' for more information. For FTP, the
# default connection is passive -- If you require an active connection, affix
# an asterisk (*) to the end of the host:port string before the path.
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
# This ftp connection is passive ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site/pub/grp/i686/athlon-xp/"
# This ftp connection is active ftp.
#PORTAGE_BINHOST="ftp://login:pass@grp.mirror.site:21*/pub/grp/i686/athlon-xp/"

# Synchronizing Portage
# =====================
#
# Each of these settings affects how Gentoo synchronizes your Portage tree.
# Synchronization is handled by rsync and these settings allow some control
# over how it is done.
#
#
# SYNC is the server used by rsync to retrieve a localized rsync mirror
#     rotation. This allows you to select servers that are geographically
#     close to you, yet still distribute the load over a number of servers.
#     Please do not single out specific rsync mirrors. Doing so places undue
#     stress on particular mirrors.  Instead you may use one of the following
#     continent specific rotations:
#
#   Default:       "rsync://rsync.gentoo.org/gentoo-portage"
#   North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
#   South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
#   Europe:        "rsync://rsync.europe.gentoo.org/gentoo-portage"
#   Asia:          "rsync://rsync.asia.gentoo.org/gentoo-portage"
#   Australia:     "rsync://rsync.au.gentoo.org/gentoo-portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
#     a current portage tree before it exits with an error. This allows
#     for a more successful retrieval without user intervention most times.
#RSYNC_RETRIES="3"
#
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
#     on a connection. Most users will benefit from this setting as it will
#     reduce the amount of 'dead air' they experience when they run across
#     the occasional, unreachable mirror. Dialup users might want to set this
#     value up around the 300 second mark.
#RSYNC_TIMEOUT=180

# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
#     program is compiled. Presently the only use is for specifying
#     the number of parallel makes (-j) to perform. The suggested number
#     for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# PORTAGE_NICENESS provides a default increment to emerge's niceness level.
#     Note: This is an increment. Running emerge in a niced environment will
#     reduce it further. Default is unset.
# PP 040918 uncomment next line
PORTAGE_NICENESS=3
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
#     packages from the system after every successful merge. This is the
#     same as running 'emerge -c' after every merge. Set with: "yes" or "no".
#     This does not affect the unpacked source. See 'noclean' below.
#AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
#     these settings are for developer use, but some are available to non-
#     developers as well.
#
#  'autoaddcvs'  causes portage to automatically try to add files to cvs
#                that will have to be added later. Done at generation times
#                and only has an effect when 'cvs' is also set.
#  'buildpkg'    causes binary packages to be created of all packages that
#                are being merged.
#  'ccache'      enables ccache support via CC.
# PP 041106 : Ccache is useful if emerge/system crashes
#             needs pkg installed to work (done)
#  'collision-protect'
#                prevents packages from overwriting files that are owned by
#                another package or by no package at all.
#  'cvs'         causes portage to enable all cvs features (commits, adds),
#                and to apply all USE flags in SRC_URI for digests -- for
#                developers only.
#  'digest'      causes digests to be generated for all packages being merged.
#  'distcc'      enables distcc support via CC.
#  'distlocks'   enables distfiles locking using fcntl or hardlinks. This
#                is enabled by default. Tools exist to help clean the locks
#                after crashes: /usr/lib/portage/bin/clean_locks.
#  'fixpackages' allows portage to fix binary packages that are stored in
#                PKGDIR. This can consume a lot of time. 'fixpackages' is
#                also a script that can be run at any given time to force
#                the same actions.
#  'gpg'         enables basic verification of Manifest files using gpg.
#                This features is UNDER DEVELOPMENT and reacts to features
#                of strict and severe. Heavy use of gpg sigs is coming.
#  'keeptemp'    prevents the clean phase from deleting the temp files ($T)
#                from a merge.
#  'keepwork'    prevents the clean phase from deleting the WORKDIR.
#  'maketest'    causes ebuilds to perform testing phases if they are capable
#                of it. Some packages support this automaticaly via makefiles.
#  'noauto'      causes ebuild to perform only the action requested and
#                not any other required actions like clean or unpack -- for
#                debugging purposes only.
#  'noclean'     prevents portage from removing the source and temporary files
#                after a merge -- for debugging purposes only.
#  'nostrip'     prevents the stripping of binaries.
#  'notitles'    disables xterm titlebar updates (which contain status info).
#  'sandbox'     enables sandboxing when running emerge and ebuild.
#  'strict'      causes portage to react strongly to conditions that are
#                potentially dangerous, like missing/incorrect Manifest files.
#  'userpriv'    allows portage to drop root privileges while it is compiling,
#                as a security measure.  As a side effect this can remove
#                sandbox access violations for users.
#  'usersandbox' enables sandboxing while portage is running under userpriv.
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
#FEATURES="sandbox ccache distcc distlocks autoaddcvs"
FEATURES="userpriv"
#
# CCACHE_SIZE sets the space use limitations for ccache. The default size is
#     2G, and will be set if not defined otherwise and ccache is in features.
#     Portage will set the default ccache dir if it is not present in the
#     user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
#     (/var/tmp/ccache), and for regular use the default is /root/.ccache.
#     Sizes are specified with 'G' 'M' or 'K'.
#     '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G).
#CCACHE_SIZE="2G"
#
# DISTCC_DIR sets the temporary space used by distcc.
#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
#     the portage tree. Specific chunks of the tree may be excluded from
#     consideration. This may cause dependency failures if you are not careful.
#     The file format is one pattern per line, blanks and ';' or '#' lines are
#     comments. See 'man rsync' for more details on the exclude-from format.
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes

# PP 041106 :  1 line  commented :
#  'man make.conf' :  /etc KDE  protected by dft
#CONFIG_PROTECT="/etc /usr/share /usr/kde"

# PP 060402 :  1 line  added fr emerge output :
EMERGE_DEFAULT_OPTS="--alphabetical"

# PP 060627 :  2 lines  fr .example
PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: elog saves messages in wrong folder

[Marc Blumentritt]

Richard Fish schrieb:
> I'm on portage 2.1.2_pre1-r1, and logs are still appearing in
> /v/l/portage/elog/ for me.  So I'm really thinking this behavior will
> only show up with particular make.conf settings.  Can either of you
> post your make.conf please?

Here it is:

cat /etc/make.conf
# These settings were set by the catalyst build script that
automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CHOST="i686-pc-linux-gnu"
#CFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe"
#CFLAGS="-march=i686 -Os -fomit-frame-pointer -pipe -msse -mmmx
-mfpmath=sse"
CFLAGS="-march=c3-2 -Os -fomit-frame-pointer -pipe -msse -mmmx -mfpmath=sse"
CXXFLAGS="${CFLAGS}"
ARCH="x86"
ACCEPT_KEYWORDS="x86"
PORTAGE_TMPDIR="/var/tmp/portage"
PORTDIR="/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
#PKGDIR="${PORTDIR}/packages"
PORTDIR_OVERLAY=""
#PORTDIR_OVERLAY="/usr/local/portage/gentoo-de ${PORTDIR_OVERLAY}"
PORTDIR_OVERLAY="/usr/local/portage/epios ${PORTDIR_OVERLAY}"
PORTDIR_OVERLAY="/usr/local/portage/my_ebuilds ${PORTDIR_OVERLAY}"
PORT_LOGDIR="/var/log/portage"
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
http://distfiles.gentoo.org "
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
PORTAGE_RSYNC_RETRIES="3"
RSYNC_TIMEOUT=180
MAKEOPTS="-j2"
PORTAGE_NICENESS=3
AUTOCLEAN="yes"
VIDEO_CARDS="via"
ALSA_CARDS="via82xx"

LINGUAS="de us"

# layman
source /usr/portage/local/layman/make.conf

# Lirc options:
LIRC_DEVICES="imon"

#PORTAGE_ELOG_CLASSES="warn error info log"
PORTAGE_ELOG_CLASSES="warn error info"
PORTAGE_ELOG_SYSTEM="save"

FEATURES="ccache distlocks userpriv parallel-fetch -buildpkg"
#FEATURES="ccache distlocks sandbox userpriv usersandbox"
CCACHE_SIZE="2G"
#USE="nptl"
USE="16bit \
-acl -adabas -adns -aim -arts -avantgo \
-bidi -bindist -bluetooth \
-canna -chipcard -cups \
-dba \
expat
fortran -foomaticdb -freewnn \
gdbm -gimp -gimpprint \
-hbci \
-icq -innodb input_devices_keyboard input_devices_mouse -ipv6 -irmc \
-jabber \
-kde -kdepim -kerberos \
-ldap \
-msn mysqli \
nptl nptlonly \
-ofx -openexr \
-pcmcia -pda php -ppds \
-rdesktop \
-samba -sametime -scanner -slp -smartcard \
unichromepro unicode \
vdr verbose video_cards_via -visualization \
win32codecs \
X -xface -xml2 \
-yahoo"

Thanks for the help in advance.
Marc

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: elog saves messages in wrong folder

[Marc Blumentritt]

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Neil Bothwick schrieb:
> On Mon, 25 Sep 2006 23:47:57 -0400, Philip Webb wrote:
> There's a little confusion here. Portage now saves all package logfiles
> in the latter format. The files you are seeing on $PORT_LOGDIR are
> probably portage logs, not elog output. Have you checked the contents of
> the files? If they contain more than the e* messages you have asked for,
> these are not your ELOG files.

OK, I checked some of the files in /var/log/portage and it is getting
stranger! I have both types of log files with the new name format. 2
examples are attached to this mail (gzipped). Both (genkernel and
linux-headers) were emerged at the same day in one update of my system.

For me, it looks like, that it depends upon chance, which type of log
file will be left on my system (it overwrites the first one, which is
saved).

Any ideas?

Marc


[-- Attachment #2: sys-kernel_linux-headers-2.6.17-r1_20060924-115355.log.gz --]
[-- Type: application/gzip, Size: 20263 bytes --]

[-- Attachment #3: sys-kernel_genkernel-3.4.1_20060924-135307.log.gz --]
[-- Type: application/gzip, Size: 552 bytes --]

Re: [gentoo-user] Re: elog saves messages in wrong folder

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 655 bytes --]

On Tue, 26 Sep 2006 10:08:20 +0200, Marc Blumentritt wrote:

> OK, I checked some of the files in /var/log/portage and it is getting
> stranger! I have both types of log files with the new name format. 2
> examples are attached to this mail (gzipped). Both (genkernel and
> linux-headers) were emerged at the same day in one update of my system.

Portage has always saved two logfiles for each emerge, one with all the
raw output and one with the e* messages. The elog options extract some,
or all depending on your settings, of the information from the the latter
file.


-- 
Neil Bothwick

"Bohtre," said Pooh, as his dyslexia worsened

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: [solved] elog saves messages in wrong folder

[Marc Blumentritt]

Neil Bothwick schrieb:
> On Tue, 26 Sep 2006 10:08:20 +0200, Marc Blumentritt wrote:
> Portage has always saved two logfiles for each emerge, one with all the
> raw output and one with the e* messages. The elog options extract some,
> or all depending on your settings, of the information from the the latter
> file.

OK. Now I did a proper check of my log situation and I realized, that
nothing is wrong here! I was just confused by the name format, as Neil
wrote, combined with the fact, that some programs do not create any
"elog", if there are no messages to log (e.g. lcdsplash).

Thanks for making this clear for me.
Marc

-- 
gentoo-user@gentoo.org mailing list