dcopserver commits suicide! Read all about it!

tireseas · 07-18-2004, 11:21 AM

Hi all

Running Slackware 10, I noticed this in ps -aux PID 1791:

Code:

andy      1788  0.0  1.8 21712 9508 ?        Ss   16:58   0:00 kdeinit: Running...
andy      1791  0.0  1.9 22068 9948 ?        S    16:58   0:00 kdeinit: dcopserver --nosid --suicide
andy      1793  0.0  2.0 23444 10620 ?       S    16:58   0:00 kdeinit: klauncher
andy      1795  0.0  2.5 23340 12904 ?       S    16:58   0:00 kdeinit: kded
andy      1798  0.0  0.3  2668 1560 pts/0    Ss   16:58   0:00 -sh

I am very curious about it and am wondering is it okay for a process to "suicide" at loading a user profile on a stand-alone machine, especially something like the dcopserver?

It doesn't appear to be impacting anything else, but ... ?

The info on dcopservers here seems to avoid the issue, so some straight goods would be useful

Cheers

foo_bar_foo · 07-18-2004, 12:26 PM

I don't understand what you are saying is the problem
that output looks perfectly normal

Proud · 07-18-2004, 12:30 PM

$: kdeinit --help
Usage: kdeinit [options]
--no-kded Do not start kded
--suicide Terminate when no KDE applications are left running

My ps aux returns a line with just kdeinit: dcopserver --nosid.

tireseas · 07-18-2004, 02:38 PM

I think there was a misunderstanding:

Quote:

Originally posted by foo_bar_foo
I don't understand what you are saying is the problem
that output looks perfectly normal

I'm expressing curiosity about whether or not this is "normal" for the dcopserver to (commit) suicide ... not that there is a problem.
I'll assume from the way your response is phrased that there is no problem.

Now I know. Thank you