1 |
On Sun, 24 Jun 2012 17:48:33 -0500 |
2 |
Dale <rdalek1967@×××××.com> wrote: |
3 |
|
4 |
> Mick wrote: |
5 |
> > On Sunday 24 Jun 2012 19:27:36 Dale wrote: |
6 |
> >> Jarry wrote: |
7 |
> >>> Hi, |
8 |
> >>> I have just checked my machines and I found I have basically |
9 |
> >>> two groups of settings ("ls -al" in /var/log/portage/elog/): |
10 |
> >>> |
11 |
> >>> A) |
12 |
> >>> drwxrws--- 2 portage root 4096 Jun 24 03:10 . |
13 |
> >>> drwxr-xr-x 3 root root 4096 Apr 7 2009 .. |
14 |
> >>> -rw-rw-r-- 1 portage root 57760 Jun 22 15:11 summary.log |
15 |
> >>> |
16 |
> >>> B) |
17 |
> >>> drwxrwsr-x 2 portage portage 4096 Jun 24 13:30 . |
18 |
> >>> drwxrws--- 3 portage portage 4096 Nov 3 2011 .. |
19 |
> >>> -rw-rw-r-- 1 portage portage 1132 Jun 22 17:28 summary.log |
20 |
> >>> |
21 |
> >>> Not only "summary.log", but also /var/log/portage/ and |
22 |
> >>> /var/log/portage/elog/ have quite different permissions. |
23 |
> >>> I'm sure I never changed it manually, the only difference |
24 |
> >>> is that "A" group has been installed 3 yers ago, while "B" |
25 |
> >>> just recently (but both regulary updated). |
26 |
> >>> |
27 |
> >>> So is the "B-version" correct one? |
28 |
> >>> |
29 |
> >>> Jarry |
30 |
> >> This is my thinking on why it may be different for different folks. |
31 |
> >> This first tho. I run emerge as root. I have not added my |
32 |
> >> regular user to the portage group. I have no memory of messing |
33 |
> >> with the permissions either. |
34 |
> >> |
35 |
> >> I think that if you use a regular user to emerge some things, it |
36 |
> >> gets set to portage:portage or some mix of portage:root. If you |
37 |
> >> always run emerge as root, then you get root:root. It may be that |
38 |
> >> this is only set once or that it could be modified if you run as |
39 |
> >> root then later on run as a user. |
40 |
> >> |
41 |
> >> For the record, mine is set to root:root. As mentioned above, I |
42 |
> >> ALWAYS run emerge as root. |
43 |
> >> |
44 |
> >> Any one have thoughts on this? |
45 |
> >> |
46 |
> >> Dale |
47 |
> >> |
48 |
> >> :-) :-) |
49 |
> > I always run emerge as root. |
50 |
> > |
51 |
> > elog is owned by portage:root, summary.log within it as |
52 |
> > portage:root, other log files within /var/log/portage are owned by |
53 |
> > portage:portage. |
54 |
> |
55 |
> So those that allow users to run would have the same permissions as |
56 |
> everyone else. Now I wonder why they vary from system to system |
57 |
> then. It seems to me, they should be the same for everyone. Just |
58 |
> seems odd. |
59 |
> |
60 |
> Dale |
61 |
> |
62 |
> :-) :-) |
63 |
|
64 |
I generally "emerge -p" as user then "emerge" as root. For ownership |
65 |
of /var/log/portage/elog, I tried changing my system with portage:root |
66 |
to portage:portage and vice versa on the other system. Something |
67 |
during right the merge phase, right around when those elog messages |
68 |
appear, resets the ownership back to what is was before I changed it |
69 |
on both systems. Odd indeed. |
70 |
|
71 |
I thought perhaps some user flag in FEATURES would do this, but the |
72 |
only difference between the two is buildpkg vs. buildsyspkg. The only |
73 |
user FEATURE enabled is userfetch. Running portage-2.2.0_alpha112 on |
74 |
both. |
75 |
|
76 |
- Bryan |