public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bryan Gardiner <bog@khumba.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Proper permissions for /var/log/portage/elog/summary.log?
Date: Sun, 24 Jun 2012 17:27:16 -0700	[thread overview]
Message-ID: <20120624172716.3e05ac32@khumba.net> (raw)
In-Reply-To: <4FE79941.7010700@gmail.com>

On Sun, 24 Jun 2012 17:48:33 -0500
Dale <rdalek1967@gmail.com> wrote:

> Mick wrote:
> > On Sunday 24 Jun 2012 19:27:36 Dale wrote:
> >> Jarry wrote:
> >>> Hi,
> >>> I have just checked my machines and I found I have basically
> >>> two groups of settings ("ls -al" in /var/log/portage/elog/):
> >>>
> >>> A)
> >>> drwxrws--- 2 portage root     4096 Jun 24 03:10 .
> >>> drwxr-xr-x 3 root    root     4096 Apr  7  2009 ..
> >>> -rw-rw-r-- 1 portage root    57760 Jun 22 15:11 summary.log
> >>>
> >>> B)
> >>> drwxrwsr-x 2 portage portage 4096 Jun 24 13:30 .
> >>> drwxrws--- 3 portage portage 4096 Nov  3  2011 ..
> >>> -rw-rw-r-- 1 portage portage 1132 Jun 22 17:28 summary.log
> >>>
> >>> Not only "summary.log", but also /var/log/portage/ and
> >>> /var/log/portage/elog/ have quite different permissions.
> >>> I'm sure I never changed it manually, the only difference
> >>> is that "A" group has been installed 3 yers ago, while "B"
> >>> just recently (but both regulary updated).
> >>>
> >>> So is the "B-version" correct one?
> >>>
> >>> Jarry
> >> This is my thinking on why it may be different for different folks.
> >> This first tho.  I run emerge as root.  I have not added my
> >> regular user to the portage group.  I have no memory of messing
> >> with the permissions either.
> >>
> >> I think that if you use a regular user to emerge some things, it
> >> gets set to portage:portage or some mix of portage:root.  If you
> >> always run emerge as root, then you get root:root.  It may be that
> >> this is only set once or that it could be modified if you run as
> >> root then later on run as a user.
> >>
> >> For the record, mine is set to root:root.  As mentioned above, I
> >> ALWAYS run emerge as root.
> >>
> >> Any one have thoughts on this?
> >>
> >> Dale
> >>
> >> :-)  :-)
> > I always run emerge as root.
> >
> > elog is owned by portage:root, summary.log within it as
> > portage:root, other log files within /var/log/portage are owned by
> > portage:portage.
> 
> So those that allow users to run would have the same permissions as
> everyone else.  Now I wonder why they vary from system to system
> then. It seems to me, they should be the same for everyone.  Just
> seems odd. 
> 
> Dale
> 
> :-)  :-) 

I generally "emerge -p" as user then "emerge" as root.  For ownership
of /var/log/portage/elog, I tried changing my system with portage:root
to portage:portage and vice versa on the other system.  Something
during right the merge phase, right around when those elog messages
appear, resets the ownership back to what is was before I changed it
on both systems.  Odd indeed.

I thought perhaps some user flag in FEATURES would do this, but the
only difference between the two is buildpkg vs. buildsyspkg.  The only
user FEATURE enabled is userfetch.  Running portage-2.2.0_alpha112 on
both.

- Bryan



  reply	other threads:[~2012-06-25  0:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-24 14:12 [gentoo-user] Proper permissions for /var/log/portage/elog/summary.log? Jarry
2012-06-24 15:19 ` Mick
2012-06-24 17:46 ` Bryan Gardiner
2012-06-24 18:27 ` Dale
2012-06-24 22:11   ` Mick
2012-06-24 22:48     ` Dale
2012-06-25  0:27       ` Bryan Gardiner [this message]
2012-06-25  3:26         ` Dale
2012-06-26 18:43     ` Tanstaafl
2012-06-25 18:19   ` Jarry
2012-06-25 22:20     ` Michael Mol
2012-06-26  6:56       ` Bryan Gardiner
2012-06-26  7:03         ` Bryan Gardiner

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=20120624172716.3e05ac32@khumba.net \
    --to=bog@khumba.net \
    --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