killing stuff at startup

phant0m · 08-15-2003, 05:53 AM

when i start my KDE i have to kill a proccess in order to get my sound working.
i do

Code:

[phantom@phntm phantom]$ ps aux | grep art
phantom   3130  0.0  0.0  4132  136 ?        S    13:48   0:00 /bin/sh /usr/bin/startkde
phantom   3236  0.2  1.7 25148 4588 ?        S    13:48   0:00 /usr/bin/artsd -F 10 -S 4096 -a toss -d -b 16 -s 60 -m artsmessage -l 3 -f
phantom   3412  0.0  0.2  3572  640 pts/2    S    13:50   0:00 grep art

and then i just kill the middle proccess (3236 in this case).

this is all fine but how can i make it not open this proccess in the first place?

P.S.
this does not seem to happen on gnome so my guess is this is a kde proccess.

MasterC · 08-15-2003, 06:24 AM

artsd is the Sound Server for KDE, so no, it wouldn't happen in Gnome

You could do a few things that are generic:
chmod a-x /usr/bin/artsd
Then it cannot be executed.
Find which package contains artsd, and if you don't need any apps in it:
rpm -e packagename

You can set it's execute bit only for root, own the file to only root and chmod so only root can execute it (better off with the first chmod thing above).

Or you can dig through your scripts and see what (if anything) is starting it. If it's KDE core, then you could (theoretically as it would probably be quite an effort) dig through the code and gut it.

Cool