Johan Nielsen wrote:
Well then it would be nice if they were represented/associated more logically to whatever process they belong/"assist".
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.
Do you mean as in: ps -f -u <user> UID PID PPID C STIME TTY TIME CMD <user> 1852 1846 0 Nov13 tty1 00:00:00 -bash <user> 1871 1852 0 Nov13 tty1 00:00:00 /bin/sh /usr/X11R6/bin/startx <user> 1872 1852 0 Nov13 tty1 00:00:00 tee /home/<user>/.X.err <user> 1884 1871 0 Nov13 tty1 00:00:00 xinit /usr/X11R6/lib/X11/xinit/xinitrc -- /usr/X11R6/lib/X11/xi <user> 1891 1884 0 Nov13 tty1 00:00:00 /bin/sh /usr/X11R6/bin/kde <user> 1914 1 0 Nov13 ? 00:00:00 kdeinit: Running... <user> 1917 1 0 Nov13 ? 00:00:02 kdeinit: dcopserver --nosid <user> 1920 1 0 Nov13 ? 00:00:00 kdeinit: klauncher <user> 1923 1 0 Nov13 ? 00:01:01 kdeinit: kded <user> 1932 1914 0 Nov13 ? 00:00:06 /opt/kde3/bin/artsd -F 10 -S 4096 -s 5 -m artsmessage -l 3 -f <user> 1934 1 0 Nov13 ? 00:00:03 kdeinit: knotify <user> 1935 1891 0 Nov13 tty1 00:00:00 kwrapper ksmserver <user> 1937 1 0 Nov13 ? 00:00:02 kdeinit: ksmserver <user> 1938 1914 0 Nov13 ? 00:00:43 kdeinit: kwin <user> 1940 1 0 Nov13 ? 00:00:03 kdeinit: kwrited <user> 1942 1 0 Nov13 ? 00:00:33 kdeinit: kdesktop <user> 1952 1 0 Nov13 ? 00:00:04 kamix <user> 1956 1 0 Nov13 ? 00:00:04 susewatcher -caption SuSE Watcher -icon kinternet.png -miniicon <user> 1957 1 0 Nov13 ? 00:00:06 suseplugger -caption SuSE Hardware Tool -icon hi22-action-hardw <user> 1993 1914 0 Nov13 ? 00:01:45 kdeinit: konqueror --silent <user> 1994 1914 0 Nov13 ? 00:08:20 kdeinit: konsole <user> 1995 1994 0 Nov13 pts/1 00:00:00 /bin/bash <user> 2008 1994 0 Nov13 pts/2 00:00:00 /bin/bash <user> 2018 1994 0 Nov13 pts/3 00:00:00 /bin/bash <user> 2028 1994 0 Nov13 pts/4 00:00:00 /bin/bash <user> 2038 1914 0 Nov13 ? 00:20:46 kvirc -m <user> 2039 1914 29 Nov13 ? 1-00:56:06 /opt/mozilla/lib/mozilla-bin <user> 2045 2039 0 Nov13 ? 00:00:00 /opt/mozilla/lib/mozilla-bin <user> 2046 2045 0 Nov13 ? 00:01:16 /opt/mozilla/lib/mozilla-bin <user> 2047 2045 0 Nov13 ? 00:00:00 /opt/mozilla/lib/mozilla-bin <user> 2048 2045 0 Nov13 ? 00:02:54 /opt/mozilla/lib/mozilla-bin <user> 2050 2038 0 Nov13 ? 00:00:00 kvirc -m <user> 2662 1 1 Nov13 ? 01:14:29 kicker --nocrashhandler <user> 2986 2045 0 Nov13 ? 00:00:00 /opt/mozilla/lib/mozilla-bin <user> 2987 2045 0 Nov13 ? 00:00:00 /opt/mozilla/lib/mozilla-bin <user> 2989 2045 0 Nov13 ? 00:00:00 /opt/mozilla/lib/mozilla-bin <user> 7022 1 0 Nov15 ? 00:00:03 kdeinit: kio_uiserver <user> 10680 1914 0 Nov16 ? 00:00:00 kdeinit: kio_file file /tmp/ksocket-<user>/klauncheryUTWsb.slave <user> 11014 2045 0 Nov16 ? 00:00:01 /opt/mozilla/lib/mozilla-bin <user> 11907 2018 0 01:26 pts/3 00:00:00 ps -fu <user> You don't have to be root, and "-f -u" can be shortened to just "-fu". ps is strange, many letters are shorthand for 2 completely different options, depending on whether or not they have a dash in front of them. For example, if I type in "ps f -u <user>" the information above is presented like this: PID TTY STAT TIME COMMAND 1852 tty1 S 0:00 -bash 1871 tty1 S 0:00 \_ /bin/sh /usr/X11R6/bin/startx 1884 tty1 S 0:00 | \_ xinit /usr/X11R6/lib/X11/xinit/xinitrc -- /usr/X11R6/lib/X11/xinit/xserverrc 1891 tty1 S 0:00 | \_ /bin/sh /usr/X11R6/bin/kde 1935 tty1 S 0:00 | \_ kwrapper ksmserver 1872 tty1 S 0:00 \_ tee /home/<user>/.X.err 7022 ? S 0:03 kdeinit: kio_uiserver 2662 ? S 74:39 kicker --nocrashhandler 1957 ? S 0:06 suseplugger -caption SuSE Hardware Tool -icon hi22-action-hardware.png -miniicon hi2 1956 ? S 0:04 susewatcher -caption SuSE Watcher -icon kinternet.png -miniicon kinternet.png --quie 1952 ? S 0:04 kamix 1942 ? S 0:33 kdeinit: kdesktop 1940 ? S 0:03 kdeinit: kwrited 1937 ? S 0:02 kdeinit: ksmserver 1934 ? S 0:03 kdeinit: knotify 1923 ? S 1:01 kdeinit: kded 1920 ? S 0:00 kdeinit: klauncher 1917 ? S 0:02 kdeinit: dcopserver --nosid 1914 ? S 0:00 kdeinit: Running... 1932 ? S 0:06 \_ /opt/kde3/bin/artsd -F 10 -S 4096 -s 5 -m artsmessage -l 3 -f 1938 ? S 0:43 \_ kdeinit: kwin 1993 ? S 1:45 \_ kdeinit: konqueror --silent 1994 ? S 8:22 \_ kdeinit: konsole 1995 pts/1 S 0:00 | \_ /bin/bash 2008 pts/2 S 0:00 | \_ /bin/bash 2018 pts/3 S 0:00 | \_ /bin/bash 11939 pts/3 R 0:00 | | \_ ps f -u <user> 2028 pts/4 S 0:00 | \_ /bin/bash 2038 ? S 20:48 \_ kvirc -m 2050 ? S 0:00 | \_ kvirc -m 5870 ? Z 0:00 | \_ [kvi_run_netscap] <defunct> 2039 ? S 1499:03 \_ /opt/mozilla/lib/mozilla-bin 2045 ? S 0:00 | \_ /opt/mozilla/lib/mozilla-bin 2046 ? S 1:16 | \_ /opt/mozilla/lib/mozilla-bin 2047 ? S 0:00 | \_ /opt/mozilla/lib/mozilla-bin 2048 ? S 2:54 | \_ /opt/mozilla/lib/mozilla-bin 2986 ? S 0:00 | \_ /opt/mozilla/lib/mozilla-bin 2987 ? S 0:00 | \_ /opt/mozilla/lib/mozilla-bin 2989 ? S 0:00 | \_ /opt/mozilla/lib/mozilla-bin 11014 ? S 0:01 | \_ /opt/mozilla/lib/mozilla-bin 10680 ? S 0:00 \_ kdeinit: kio_file file /tmp/ksocket-<user>/klauncheryUTWsb.slave-socket /tmp/ksoc And yes, "f -f" is a valid combination. Oh, in case you're wondering, kicker crashes on me a lot, and I restart it from <DesktopMenu>/Run. That's why it's listed above as not having been started by kdeinit.