kdeinit running more then once
Have not found manpages for kdeinit and my web connection is so bad that a Google for the moment is not possible. Therefor to the list, why is kdeinit running four times with different pid numbers on my 9. box? Is that normal?
On Friday 01 October 2004 18:51, Constant Brouerius van Nidek wrote:
Have not found manpages for kdeinit and my web connection is so bad that a Google for the moment is not possible. Therefor to the list, why is kdeinit running four times with different pid numbers on my 9. box? Is that normal?
Press <Ctrl>-<Esc> to get a KDESystemGuard Process table, and see if they are there as well (compare the pid#). Cheers, Leen
Lørdag den 2. oktober 2004 12:18 skrev Leendert Meyer:
On Friday 01 October 2004 18:51, Constant Brouerius van Nidek wrote:
Have not found manpages for kdeinit and my web connection is so bad that a Google for the moment is not possible. Therefor to the list, why is kdeinit running four times with different pid numbers on my 9. box? Is that normal?
Press <Ctrl>-<Esc> to get a KDESystemGuard Process table, and see if they are there as well (compare the pid#).
I have also noticed a lot (way to many kdeinits) when using ps -A is there a logical explaination !! TIA Johan
Johan Nielsen wrote:
On Friday 01 October 2004 18:51, Constant Brouerius van Nidek wrote:
Therefor to the list, why is kdeinit running four times with different pid numbers on my 9. box? Is that normal?
Yes.
I have also noticed a lot (way to many kdeinits) when using ps -A is there a logical explaination !!
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe, On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system: ├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit] It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
-- Joe Morris
Randall Schulz
Lørdag den 2. oktober 2004 17:12 skrev Randall R Schulz:
Joe,
On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system:
├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit]
It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
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. Johan
On Saturday 02 October 2004 22:41, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 17:12 skrev Randall R Schulz:
Joe,
On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system:
├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit]
It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
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.
Man, you really need to learn to STFW. ;) Killing a kdeinit process is like shooting oneself in the foot. Did a bit of STFW for you, and: Here is a thread of 3 messages about kdeinit. Although their KDE is running on FreeBSD, it is still KDE and still the same issue. And I say 'issue', not 'problem'. ;P http://freebsd.kde.org/pipermail/kde-freebsd/2003-March/004359.html Click a few times on the link right behind 'Next message' to read all 3 messages. I'm quite sure that more STFW will gain you more understanding. Cheers, Leen
On Saturday 02 October 2004 2:28 pm, Richard Bos wrote:
Op zaterdag 2 oktober 2004 23:11, schreef Leendert Meyer:
STFW
WIT (What Is That ;) ?
Modern version of RTFM... Search the F web Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.5-7.108-default x86_64
* Richard Bos <radoeka@xs4all.nl> [10-02-04 16:29]:
Op zaterdag 2 oktober 2004 23:11, schreef Leendert Meyer:
STFW
WIT (What Is That ;) ?
Just like RTFM, but substitute search and web. dict STFW wtf STFW -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Lørdag den 2. oktober 2004 23:28 skrev Richard Bos:
Op zaterdag 2 oktober 2004 23:11, schreef Leendert Meyer:
STFW
WIT (What Is That ;) ?
his way of complaining that I haven't spend enough time diving into the inner workings of linux. http://www.science.uva.nl/~mes/jargon/s/stfw.html
-- Richard Bos Without a home the journey is endless
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! I'm off for a ride, now. When I get back, I'll let you know how much faster I can ride with less rotating mass and wind resistance from my wheels!
...
Cheers,
Leen
RRS
* Randall R Schulz <rschulz@sonic.net> [10-02-04 16:37]:
I'm off for a ride, now. When I get back, I'll let you know how much faster I can ride with less rotating mass and wind resistance from my wheels!
Hope you *get* back. :^) -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
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
Leen, On Saturday 02 October 2004 17:14, Leendert Meyer wrote:
On Saturday 02 October 2004 23:33, Randall R Schulz wrote:
...
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.
Uh... That was sarcasm. The point being that just because something is incorporated into an engineering design more than once does not imply that it's redundant (or that the redundancy is a bad thing) and can be arbitrarily removed without affecting the proper function of the designed system, whatever it may be (hardware or software, vehicle or computer, etc.)
Cheers,
Leen
By the way, you all will be happy to know that the hospital I'm in since this afternoon's bike ride went horribly wrong (who'd have thought that spokes sustained peak stresses when braking?) has internet terminals in every room, so I'll be able to maintain my critical presence here on the SuSE Linux (English) list. Wish me well, OK? I hear they can do amazing things with mangled spines these days. Randall Schulz
Op zondag 3 oktober 2004 02:58, schreef Randall R Schulz:
Uh... That was sarcasm. The point being that just because something is incorporated into an engineering design more than once does not imply that it's redundant (or that the redundancy is a bad thing) and can be arbitrarily removed without affecting the proper function of the designed system, whatever it may be (hardware or software, vehicle or computer, etc.)
After pulling out all my hairs but one I see what you mean... Regards, -- Jos van Kan
söndag 03 oktober 2004 02:14 skrev Leendert Meyer:
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.
Ok, so AFAUK .. kdeinit => {} o prcs. Ain't life grand :-)
Lørdag den 2. oktober 2004 23:11 skrev Leendert Meyer:
On Saturday 02 October 2004 22:41, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 17:12 skrev Randall R Schulz:
Joe,
On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system:
├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit]
It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
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.
Man, you really need to learn to STFW. ;)
I do but didn't get down to this one as things work but I was just curious about the question
Killing a kdeinit process is like shooting oneself in the foot.
Well I can see that I killed some kdeinits related to Kontact aka kmail mainly ;-) Damn - Kmail / Kontact shouldn't have all those sockets "hanging around" all the time
Did a bit of STFW for you, and:
Here is a thread of 3 messages about kdeinit. Although their KDE is running on FreeBSD, it is still KDE and still the same issue. And I say 'issue', not 'problem'. ;P
http://freebsd.kde.org/pipermail/kde-freebsd/2003-March/004359.html
Very informative link - TY
Click a few times on the link right behind 'Next message' to read all 3 messages.
I'm quite sure that more STFW will gain you more understanding.
Sure - but we can't all know everything that includes a proper searchphrase for this issue.
Cheers,
Leen
On Sunday 03 October 2004 03:49, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 23:11 skrev Leendert Meyer:
On Saturday 02 October 2004 22:41, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 17:12 skrev Randall R Schulz:
Joe,
On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system:
├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit]
It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
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.
Man, you really need to learn to STFW. ;)
I do but didn't get down to this one as things work but I was just curious about the question
Killing a kdeinit process is like shooting oneself in the foot.
Well I can see that I killed some kdeinits related to Kontact aka kmail mainly ;-)
Damn - Kmail / Kontact shouldn't have all those sockets "hanging around" all the time
Did a bit of STFW for you, and:
Here is a thread of 3 messages about kdeinit. Although their KDE is running on FreeBSD, it is still KDE and still the same issue. And I say 'issue', not 'problem'. ;P
http://freebsd.kde.org/pipermail/kde-freebsd/2003-March/004359.html
Very informative link - TY
Click a few times on the link right behind 'Next message' to read all 3 messages.
I'm quite sure that more STFW will gain you more understanding.
Sure - but we can't all know everything that includes a proper searchphrase for this issue.
Ok, being curious myself, STFW revealed this: http://docs.kde.org/cgi-bin/desktopdig/search.cgi?show=en/HEAD/kdevelop/kdearch/nettransparency.html&collection=en&q=kdeinit scroll down, there's an informative paragraph with a blue highlighted 'kdeinit'. And this: http://www.kde.org/areas/sysadmin/startup.php A quote from the latter: "The drawback is that programs started this way appear as kdeinit in the output of top and ps." There. I said I would not STFW. I lied. ;)) Cheers, Leen
Søndag den 3. oktober 2004 05:11 skrev Leendert Meyer:
On Sunday 03 October 2004 03:49, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 23:11 skrev Leendert Meyer:
On Saturday 02 October 2004 22:41, Johan Nielsen wrote:
Lørdag den 2. oktober 2004 17:12 skrev Randall R Schulz:
Joe,
On Saturday 02 October 2004 06:05, Joe Morris (NTM) wrote:
...
kdeinit is the 'mother' process to start many different programs. Try ps aux to see exactly which programs. For example, on mine kdeinit starts dcopserver, klauncher, kded, knotify, ksmserver, kwin, kdesktop, kicker, etc.
The way to see how they relate is to use "pstree." Here's an excerpt from its output on my system:
├─kdeinit─┬─artsd │ ├─gaim │ ├─java │ ├─5*[kdeinit] │ ├─kdeinit─┬─3*[bash] │ │ ├─bash───pstree │ │ └─su───bash │ └─mozilla───run-mozilla.sh───mozilla-bin ├─11*[kdeinit]
It looks like at the moment I have 17 of them running! So what. They're presumably doing their thing to make my KDE experience a wonderful one, as it always is.
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.
Man, you really need to learn to STFW. ;)
I do but didn't get down to this one as things work but I was just curious about the question
Killing a kdeinit process is like shooting oneself in the foot.
Well I can see that I killed some kdeinits related to Kontact aka kmail mainly ;-)
Damn - Kmail / Kontact shouldn't have all those sockets "hanging around" all the time
Did a bit of STFW for you, and:
Here is a thread of 3 messages about kdeinit. Although their KDE is running on FreeBSD, it is still KDE and still the same issue. And I say 'issue', not 'problem'. ;P
http://freebsd.kde.org/pipermail/kde-freebsd/2003-March/004359.html
Very informative link - TY
Click a few times on the link right behind 'Next message' to read all 3 messages.
I'm quite sure that more STFW will gain you more understanding.
Sure - but we can't all know everything that includes a proper searchphrase for this issue.
Ok, being curious myself, STFW revealed this:
http://docs.kde.org/cgi-bin/desktopdig/search.cgi?show=en/HEAD/kdevelop/kde arch/nettransparency.html&collection=en&q=kdeinit
scroll down, there's an informative paragraph with a blue highlighted 'kdeinit'.
And this: http://www.kde.org/areas/sysadmin/startup.php
A quote from the latter: "The drawback is that programs started this way appear as kdeinit in the output of top and ps."
There. I said I would not STFW. I lied. ;))
Cheers,
Leen
Yes and now it's off to bed ;-)
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.
< Sorry ..... TOP posting ....> Very nice ;-) (looking up from the cabinet where I've been assembling my new AMD 64 system ;-) ) Onsdag 17 november 2004 08:41 skrev Darryl Gregorash:
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.
participants (11)
-
Constant Brouerius van Nidek -
Darryl Gregorash -
Joe Morris (NTM) -
Johan Nielsen -
Jos van Kan -
Leendert Meyer -
Patrick Shanahan -
Randall R Schulz -
Richard Bos -
Scott Leighton -
Örn Hansen