| 1 |
* Nikos Chantziaras <realnc@×××××.de> [120218 14:59]: |
| 2 |
> This isn't an important issue, but it still bugs me a bit (curiosity |
| 3 |
> killed the cat.) Some while ago (no idea when exactly, could be 6 |
| 4 |
> months ago or a year ago), I stopped being able to use "elogv" as a |
| 5 |
> regular user. Something had changed the permissions of the |
| 6 |
> "/var/log/portage" and "/var/log/portage/elog" directories. The only |
| 7 |
> thing I know for sure, is that it wasn't me who changed them (and I'm |
| 8 |
> the only user of that machine.) |
| 9 |
> |
| 10 |
> See the related bug report: |
| 11 |
> |
| 12 |
> https://bugs.gentoo.org/show_bug.cgi?id=404413 |
| 13 |
> |
| 14 |
> So I have a question: did anyone else here notice this as well? What is |
| 15 |
> the output of: |
| 16 |
> |
| 17 |
> ls -ld /var/log/portage /var/log/portage/elog |
| 18 |
> |
| 19 |
> on your system? |
| 20 |
> |
| 21 |
|
| 22 |
I seem to remember an emerge that changed the permissions of some log |
| 23 |
files (I had to change /etc/syslog-ng/syslog-ng.conf to add the |
| 24 |
owner(root) and group(logcheck) options.) |
| 25 |
|
| 26 |
I don't know if other files changed or if the directory permissions |
| 27 |
changed at that time? |
| 28 |
|
| 29 |
Todd |
Archives