Ed wrote
On 11/22/2012 12:29 PM, R. G. Newbury wrote:
I have turned off 'Desktop Search' in Settings. I have deleted all executables in /usr/bin with 'nepomuk' in the name (and virtuoso). I have nuked the nepomuk folders hiding down in ~/.kde. But after I rebooted I*still* ended up with a 'nepomukserver' running. ps -aux says it is started by kde4init. Setting 'autostart' to false in/usr/share/./autostart/nepomukserver.desktop stops that from happening, but*where* is the executable instance which kdeinit is starting? I wish to nuke it too.
FWIW, I have unchecked "Nepomuk Sematic Desktop" in the Desktop Search section of the KDE "System Settings" and upon clicking apply the server is no longer running.
Only /usr/bin/nepomukcontroller remains.
I am quite sure that that's the first thing I did. Noted as the first item. I then nuked every executable I could find. So if I failed to 'Apply' the setting, where is the executable which kdeinit *then* started. .
System Settings -> Startup and Shutdown -> Service Manager. Uncheck Nepomuk Search Module.
Login and Logout if required. No need to "nuke" anything. Well, maybe virtuoso.
Gabriel
Thanks. What a stupidly obtuse system for wasting cycles. I didn't even know that there was another complete level of 'service' management. Now it is turned off, it still does not answer the question:
Where is the damn executable which the service starts.
This sort of layered obscurity pisses me off. And the user cannot nuke the libs, since they are "dependencies" of all sorts of other actually useful bits of the install. Geoff
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 23 Nov 2012, R. G. Newbury wrote:
Thanks. What a stupidly obtuse system for wasting cycles. I didn't even know that there was another complete level of 'service' management. Now it is turned off, it still does not answer the question:
Where is the damn executable which the service starts.
This sort of layered obscurity pisses me off. And the user cannot nuke the libs, since they are "dependencies" of all sorts of other actually useful bits of the install.
Well, I think is a little bit complicated.
I guess the whole thing works like this (not 100% sure):
- - if /usr/bin/nepomukserver exist, when is started.
- - if /usr/bin/nepomukserver is missing, then a process (a thread?) is created by /usr/bin/kdeinit4 (you can change the process name once the program has been started by modifying argv[0] or you can use prctl(PR_SET_NAME, ...) for a thread - sorry but I'm not a kde developer so this is my best guess).
How can you test this:
1. Make sure /usr/bin/nepomukserver exist.
2. Logout, login.
3. In a terminal run "pstree -acgp" Notice the nepomukserver's PIDs.
4. ls -l /proc/<PID>/exe (replace <PID> with the actual PID. It should be a link to /usr/bin/nepomukserver
5. Rename /usr/bin/nepomukserver.
Repeat step 2 to 4. In step 4 the link should point now to /usr/bin/kdeinit4.
Gabriel
- --
// Gabriel VLASIU // // OpenGPG-KeyID : 44952F15 // OpenGPG-Fingerprint: 4AC5 7C26 2FE9 02DA 4906 24B2 D32B 7ED7 4495 2F15 // OpenGPG-URL : http://www.vlasiu.net/public.key