I'd like to take a look at your utility. It may be of use in other cases.
Would you post the source code, or a link to where the code may be found?
Thanks.
Loye Young
On Tue, Feb 24, 2009 at 3:47 PM, Vladimir wrote:
> After seeing that the discussion goes nowhere and nobody in charge is
> willing to do anything about this problem, I chose my own solution. It
> is ugly, dirty, but it works for now.
>
> I wrote in C program with only one instruction: exit. I have replaced
> the huge console-kit-daemon in /usr/sbin with this "program" and bingo.
> It works. No more 60+ threads. And the funny stuff is here: System seems
> to work just as before. In other words IT DOES NOT NEED FOR THIS
> MONSTER. Console kit daemon is completely useless utility.
>
> For those of you, who want to "solve" this problem I am attaching here
> my console-kit-daemon utility. Please keep in mind this is only
> temporary solution and it is far from perfect.
>
>
>
Rock on, Vlad!
I'd like to take a look at your utility. It may be of use in other cases.
Would you post the source code, or a link to where the code may be found?
Thanks.
Loye Young
On Tue, Feb 24, 2009 at 3:47 PM, Vladimir wrote:
> After seeing that the discussion goes nowhere and nobody in charge is
> willing to do anything about this problem, I chose my own solution. It
> is ugly, dirty, but it works for now.
>
> I wrote in C program with only one instruction: exit. I have replaced
> the huge console-kit-daemon in /usr/sbin with this "program" and bingo.
> It works. No more 60+ threads. And the funny stuff is here: System seems
> to work just as before. In other words IT DOES NOT NEED FOR THIS
> MONSTER. Console kit daemon is completely useless utility.
>
> For those of you, who want to "solve" this problem I am attaching here
> my console-kit-daemon utility. Please keep in mind this is only
> temporary solution and it is far from perfect.
>
>
>