I am explaining you about the restarting Nepomuk and its services. The Nepomuk services are controlled by the nepomuk server application Which is started on KDE login. The nepomuk server will take care of starting and stopping all services. It is possible to stop the server and all services altogether by simply calling a D-Bus method:
# Qdbus org.kde.NepomukServer / nepomuk server \
org.kde.NepomukServer.quit
It can then be restarted by simply calling nepomuk server again. In many situations it might be debugging of interest to pipe the output of the server (and all services) to a file:
Nepomuk server # 2> / tmp / nepomuk.stderr
So interesting to know is that Nepomuk defines a set of debugging areas for the services and the server itself. Use kdebugdialog to enable or disable them. Or one can stop and start single services. In most cases this is sufficient since each service is run in its own process. Thus, changes to a service plugins will be picked up directly:
# Qdbus org.kde.NepomukServer / service manager \
org.kde.nepomuk.ServiceManager.stopService <servicename>
# Qdbus org.kde.NepomukServer / service manager \
org.kde.nepomuk.ServiceManager.startService <servicename>
Bookmarks