| 1 |
On Sun, 2004-08-15 at 10:34, nixnut wrote: |
| 2 |
> >>For some reason syslog-ng finds it necessary to write to /proc/kmsg. The |
| 3 |
> >>policy does not allow this, so syslog-ng fails to start. Syslog-ng |
| 4 |
> >>complains that it can't open /proc/kmsg for reading, but according to |
| 5 |
> >>the policy it does have the rights to do so. |
| 6 |
> >> |
| 7 |
> > |
| 8 |
> >This is a broken syslog-ng behavior. I fixed the policy for this a |
| 9 |
> >while ago, but it hasn't gone out yet because I've been away for the |
| 10 |
> >last month+. |
| 11 |
> > |
| 12 |
|
| 13 |
> Ah, I thought as much. Shouldn't syslog-ng get fixed then instead of the |
| 14 |
> policy ;-) |
| 15 |
|
| 16 |
Let us know when you have a patch for syslog-ng |
| 17 |
|
| 18 |
|
| 19 |
> Could you post what I should change in the policy? |
| 20 |
> |
| 21 |
> Oh, and thanks for the quick reply! |
| 22 |
> |
| 23 |
> regards, |
| 24 |
> nixnut |
| 25 |
> |
| 26 |
> -- |
| 27 |
> gentoo-hardened@g.o mailing list |
| 28 |
-- |
| 29 |
Ned Ludd <solar@g.o> |
| 30 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |
Archives