[PATCH] moved abrt.socket and abrtd.lock into /var/run/abrt

[Jiri Moskovcak]

selinux allows abrtd to do anything in /var/run/abrt, so moving .socket
and .lock there so we can unlink() them without writing a selinux
policy. I wanted to move even the .pid file there, but it seems that
it's supposed to be in /var/run/abrtd.pid as some init functions expects
it there (status abrtd won't find the pid file).

J.

[Jiri Moskovcak]

Since the deadline is today, can anyone please take a look at this? I
tested it and it seems to work fine. (I tried to catch python, C and the
selinux is quiet).

Thank you,
Jirka

On 07/27/2010 05:53 PM, Jiri Moskovcak wrote:
>  selinux allows abrtd to do anything in /var/run/abrt, so moving
> .socket
>  and .lock there so we can unlink() them without writing a selinux
>  policy. I wanted to move even the .pid file there, but it seems that
>  it's supposed to be in /var/run/abrtd.pid as some init functions expects
>  it there (status abrtd won't find the pid file).
>  
>  J.

[Denys Vlasenko]

On Wed, 2010-07-28 at 09:53 +0200, Jiri Moskovcak wrote:
>  Since the deadline is today, can anyone please take a look at this?
> I
>  tested it and it seems to work fine. (I tried to catch python, C and the
>  selinux is quiet). 
I looked at the patch, it looks good to me.
-- 
vda

[Jiri Moskovcak]

On 07/28/2010 11:39 AM, Denys Vlasenko wrote:
>  On Wed, 2010-07-28 at 09:53 +0200, Jiri Moskovcak wrote:
> > Since the deadline is today, can anyone please take a look at this? I
> > tested it and it seems to work fine. (I tried to catch python, C and the
> > selinux is quiet).
>  
>  I looked at the patch, it looks good to me. 
Ok, going to push it.

Thanks for the review,
Jirka