[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-user
Subject:    [gentoo-user] Re: RFC: are you able to use "elogv" as a non-root user?
From:       Nikos Chantziaras <realnc () arcor ! de>
Date:       2012-02-19 3:08:13
Message-ID: jhpp2v$tc1$1 () dough ! gmane ! org
[Download RAW message or body]

On 19/02/12 04:00, Dale wrote:
> Alan McKinnon wrote:
>> On Sat, 18 Feb 2012 22:28:11 +0200
>> Nikos Chantziaras<realnc@arcor.de>  wrote:
>>
>>> This isn't an important issue, but it still bugs me a bit (curiosity
>>> killed the cat.)  Some while ago (no idea when exactly, could be 6
>>> months ago or a year ago), I stopped being able to use "elogv" as a
>>> regular user.  Something had changed the permissions of the
>>> "/var/log/portage" and  "/var/log/portage/elog" directories.  The
>>> only thing I know for sure, is that it wasn't me who changed them
>>> (and I'm the only user of that machine.)
>>>
>>> See the related bug report:
>>>
>>>     https://bugs.gentoo.org/show_bug.cgi?id=404413
>>>
>>> So I have a question: did anyone else here notice this as well?  What
>>> is the output of:
>>>
>>>     ls -ld /var/log/portage /var/log/portage/elog
>>>
>>> on your system?
>>>
>>>
>>
>> I use elogviewer in preference to elogv, no issues here. My perms:
>>
>> # ls -ld /var/log/portage /var/log/portage/elog
>> drwxrws--- 3 portage portage 315392 Feb 18 12:19 /var/log/portage
>> drwxrwsr-x 2 portage portage  24576 Feb 18 12:19 /var/log/portage/elog
>>
>>
>
>
> I changed mine to run as root a long time ago.  I could view the logs
> but I could not delete the old ones when I was done.  That would give a
> permissions error.  I just tried it again just now as a user and it
> spits out this when I try to clear the logs:
>
> OSError: [Errno 13] Permission denied:<some file name here>
>
> I would think that is normal.  Viewing logs can be done by everyone but
> clearing requires more permissions.

No, it's not normal.  If your user is in the portage group, then you 
should be able to delete portage logs.  So it seems your system is 
suffering from the same thing.

The fix for this is in the bug report I linked to, btw.


[prev in list] [next in list] [prev in thread] [next in thread]