Just noticed that portage.log is hardwired to be rw-rw----. This is bad for loganalyzers, plus when one tries to fix that via chmod, the time the next 'emerge' is run, its broken again. Please dont use chmod / chown for log files in a normal program like emerge (this is really the logrotators job, or the sysadmins'). Reproducible: Always Steps to Reproduce: 1.run emerge 2.see your loganalyzer bork because it is unable to read /var/log/emerge.log 3.fix it via chmod o+r /var/log/emerge.log 4.run emerge 5.see that permissions are broken again 6.fix it via chmod o+r /var/log/emerge.log 7.... you get the idea Actual Results: modified permissions of logfile(s?) Expected Results: leave permissions and ownership of logfiles as I put them Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5) ================================================================= System uname: 2.6.5 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.4.9 ccache version 2.2 [disabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3,sys-devel/automake-1.8.2-r9 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /opt/quake3/cpma/server.cfg /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /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/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs loadpolicy nodowngrade sandbox userpriv usersandbox" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http: //ftp.easynet.nl/mirror/gentoo/ ftp://gentoo.ccccom.com" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-x86-portage" USE="X aalib acl acpi alsa apache2 apm avi berkdb cdr cjk crypt cups directfb dvd encode foomaticdb gdbm ggi gif gnome2 gphoto2 gpm gtk2 guile imlib java jpeg libg++ libwww lufsusermount mad mikmod mmx mozilla moznoirc moznomail mozsvg mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png postgres python quicktime readline sane sane-backends sane-frontends scanner sdl slang spell sse ssl tcpd tetex threads tiff truetype utf8 x86 xft xinerama xml2 xv zlib"
portage:portage ug+rw is required... I have modified the code to be more polite to your situation, and it shouldn't reset the permissions any longer, but if you were to modify them away from group portage, you might be able to prevent portage from operating.
You mean by modifying the permissions of the emerge.log in a way that portage itself cannot write to it anymore ? That would be stupid of me ;) But as long as it leaves at least the world bits intact, its alright when it resets the remainder to a static owner/group/owner-group-permission-mask [although I'm still not convinced that this is good, but maybe it really is helping in terms of foolproofness which is important especially for people like me ^^]. I change to 'FIXED' since what I had in mind should work now... Thanks :)
