On Saturday 02 October 2004 23:33, Randall R Schulz wrote:
Leen,
On Saturday 02 October 2004 14:11, Leendert Meyer wrote:
On Saturday 02 October 2004 22:41, Johan Nielsen wrote:
...
I tried killing a few of them standing there all by themself and that didn't take anything down/stop running appz (at least not what I noticed).
Of course you can't kill them all but quite a lot of them actually.
Man, you really need to learn to STFW. ;)
Killing a kdeinit process is like shooting oneself in the foot.
What you talkin' about?? I decided it was stupid to have so many spokes in my bicycle wheel, so I just cut a bunch of them out. And guess what? The wheel still spins just fine!
Ok, ok, it's just 'as far as I know'. And: AFAK, kdeinit is just a wrapper around other processes. Imagine a wrapper around ssh, or kdm, or X. Kill the wrapper, and you'll kill ssh, kdm, or X. Poof. Wheel gone. But I'd better come with proof, e.g. some kind of kdeinit documentation from one of the *.kde.org sites. But I'm not going to STFW for you. ;) Please see my remarks as a hint or a sign like: "Hey, could he be right? What if he /is/ right? Where can I find more on this?". BTW, if you did STFW, and you found a good explanation of the kdeinit process, please post a pointer in this thread, and add ' - SOLVED' or so to the subject of the message. It would make life a bit easier for your successors who are trying to figure out what those kdeinit processes are, or my successors, who are trying to answer the questions of your successors. ;) Cheers, Leen