The code tags didn't help much in lining up the text.

The important field is CMD which is "kdm". Since the process had clobbered its arguments, you couldn't tell much from "ps -f". So now you know what the process is. kdm has forked a child process, but it did not exec another program.

Also pid is the process id of this process. ppid is the process id of the parent of this process. Should the parent die, this ppid will change to 1. That did not happen, so this this processs cannot be orphaned.

That's about all that you can gleen from this ouput, but it does answer a couple of questions that you raised. I'm not a kdm expert so I don't know how to stop this process from coming into existence which seems to be what you want.